Of course, we will take your OPC-UA compatible API's but we realize that most OEMs don't have those, so what we need from a technical standpoint is fairly simple. Most manufacturers have some kind of software tool that customers use to prepare jobs and send them to the printer and monitor the progress of jobs as they are processing. This software usually works over a local network. We just need some of the technical specifications on the protocol that is used by the OEM software so that we can update our software to understand how to query the printer for its current status and interpret the response. In some situations, if the software is sufficiently modular we can reuse one or more dynamic libraries that ships with the OEM software. Otherwise, a few conversations with a software engineer that is familiar with the communications protocols is usually enough for us…