Can you outline why your team embarked on this project and the problem that needed to be solved?
In my previous article, I discussed how procurement teams can help their businesses when buying support or services for open source software. There is another key issue procurement teams will have to understand in relation to implementations of this type–cloud.
Procurement is old. Just how old you ask? Well,
a long time ago in a galaxy far, far away… it’s been around for millennia. As a natural function of trade and commerce, it developed organically during the earliest civilizations. Papyrus records indicate procurement can be traced as far back as the Egyptians (the first Jedi) in 3000 B.C.
“Open source” describes a specific approach to creating, distributing and using software. Anyone can see how the source code for this software is put together, they can often use this software for free and they can potentially alter it to meet their own needs. But, if something is free, why do procurement teams need to get involved, and when can it lead to potential headaches?
Among those using automation in business, it’s common knowledge that Robotic Process Automation (RPA) can be used to connect workflow systems without the need for complex scripting and Application Programming Interfaces (APIs.) Put simply, automation software joins different parts of your business infrastructure in an often-simple way.