Why a VMS’ Integration Approach Matters (Even to Non-Techies)
- It takes the integration development process off of the project’s critical path: It used to be that a project’s go-live date was often driven by a software release schedule. With IQNtegrator, integrations are developed and deployed outside of software release schedules and that let’s you determine when to go live according to what makes the most sense for your company and program (of course other things are now on the critical path, guess we’ll have to chat about what those are later).
- It reduces the level of effort required to build integrations: IQNtegrator is drag-and-drop simple. All it takes for most integrations is a client’s business analyst (not a developer!) sitting down with our application architects and quickly mapping out both the integration process (that boring system connection, transport, and security stuff) and mapping what data goes where, testing it out, and deploying. I was talking to one of our architects the other day and he’d just finished building out a user feed and cost center load (with an associated hierarchy used to drive approvals) in a total of two hours!
- It greatly improves quality: One of my biggest worries when I used to manage implementation projects was missing an integration requirement (Uh, wait, you mean a user feed requires the user’s name?). When that happened we had to go through a new cycle of defining the requirement, amending the code, testing, and deploying. Now when that happens, the aforementioned analysts just sit back down, make the change, and we’re good to go. This is also a key value of IQNtegration once the program is up-and-running and those inevitable changes occur; we just update IQNtegrator and the program continues humming along.