Today is continuing on yesterday’s note and for the CIOs/integrator, and specifically looking at the first thing to keep in mind: familiarity with the tech stack going from the application layer all the way down to the infrastructure.

This may sound simple, but don’t underestimate the complexity. Some of this you can pick up on during the initial due diligence covering maybe a component or two. However, it won’t give you the full picture. Some of this you won’t be able to get until after the deal closes. Then it is go time!

How do you get this lay of the land?

The first criteria is to look at the I/O. The data in motion and at rest. What are the dependent services? Databases, messaging queues, third-party services, etc. How much of this is to be replicated in the acquirer’s system? Does it even need to be replicated?

The second criteria looks at the application stack. How is it built (language, build tools, platform, etc)? What does it need to function? This is looks at the hardware required to run things, and the build and deployment infrastructure to run it. What do you already have, and how much effort would it take for this to interoperate in your own ecosystem? Are there any security concerns or issues that will require having it segregated from the rest of your IT infrastructure?

The third criteria goes towards the maintenance and support going forward. What licenses are required from vendors to run the software, documentation and other essential artifacts that must be migrated? Things such as how to make changes, what changes or issues are currently outstanding, and impact of such changes.

Now ask these same questions for each of the applications or components being conveyed post-acquisition. There should be some pattern that begins to form, and from that pattern, you can start to ask questions leading to the next area of focus of your own infrastructure. What you can support, and what you will need to support.

What are some of the other questions to ask yourself when it comes to identifying the ins and outs for the custom app?

cab