“With which systems do you interface?” might be one of the most asked questions whenever IT executives enter software evaluation discussions. When IT executives ask about software integration, what they’re really asking is: ‘how will you make sure the interface is set up in a couple of days instead of a couple of months?’ To […]
“With which systems do you interface?” might be one of the most asked questions whenever IT executives enter software evaluation discussions. When IT executives ask about software integration, what they’re really asking is: ‘how will you make sure the interface is set up in a couple of days instead of a couple of months?’
To already answer the main question, Binocs seamlessly interfaces with these software products, including in-house tools:
Where is this fear of interfaces coming from?
Interfacing requires two systems to understand each other. The typical interface approach uses code & programming to transform data from the sending system, so the receiving system understands.
This is a rigid approach as it requires a clear contract and requirements upfront, making it challenging to make changes after the fact. The coding requires quite some time of scarce internal IT resources. Not only to write the initial interface but also to cope with the inevitable changes afterwards.
So ‘with which systems do you interface’ is a very relevant question.
So, in theory, a standard interface would solve this
In a lab context, there are dozens of different LIMS, ELN, LES, … systems, each unique in how and what kind of data they capture. Offering a standard interface with each and every (lab management) system out there would, in theory, solve the issue of long and painful interface setups.
However, labs differ in their ways of working. Even if they are using the same lab management systems, the setup is customized to reflect that reality. Consequently, even if two interfaces with the same LIMS system need to be setup, the ‘standard’ interface needs to be adapted to how each LIMS system X is set up/configured.
Standard is not really standard if you need to tweak it to make sure it works with a specific configuration/setup. To summarize: in theory, a standard interface sounds great, but in a context where custom configurations are common, standard interfaces are not at all a guarantee you can set up the interface in a couple of days instead of a couple of months.
We’ve managed to set up these interfaces in a matter of days, instead of weeks or months. Not because we’ve built standard interfaces with all these systems, but because we’ve taken a radically different route called zero-code interfacing.
Zero-code interfacing means that data doesn’t have to be ‘ready’ before sending it to Binocs. Interfaces upload data in whatever format it’s available to Binocs. No coded transformation and logic are needed. Instead, the transformation logic is configured directly in Binocs, using business rules (= rules that are understandable & configurable by business users). That’s why Binocs can connect to ‘any’ system with relevant data and why we can set up an interface in days instead of months.
Moreover, as the transformation logic is configured for and by the business users, it’s easy to adapt, fine-tune and scale.
Stay tuned for our next blog on zero-code interfacing, where we deep-dive into how it works, or get in touch if you can’t wait to see more!
Business process automation: accelerating change in the pharma sector
This blog post explores the different levels of business process automation and what this means for the future of integrated systems for pharma planning
Operational integration with VEEVA Vault RIM Binocs is used for capacity and operational planning in regulatory affairs and uses a RIM system (Regulatory Information Management) as a source of demand….