We are beating our ears with Kuwait WhatsApp Number List intelligence based on Big Data, to do digital transformation. The other day I was exploring the opportunity to take SaaS software for our payroll. In discussion with the sales manager of the company in question, I ask the question of the supply of the system in payroll variables: days of leave, sickness, bonus, advance of expenses … I was amazed to hear: “There is no API for this. Our customers don’t ask us. We have a formatted excel spreadsheet to fill out and upload to the system ”. I thought back to Steve Jobs’ aphorism: “When you asked people [customers] what cell phone they wanted in the 2000s, they asked for smaller phones with a battery that lasted longer.
So it’s good to listen to the customer, but to court her unexpressed needs is even better. Another example: the bank. When we want to transfer payments, via an ISO 20022 XML file, there is no way to automate at reasonable costs. You have to connect with a login, password and token, the first time to get to the management web interface, then a second time to connect to the file transfer service: login, password and token. In total, minimum 5 minutes of time. Fortunately, we spend several dozen lines of transfer per file, otherwise we would spend these 5 minutes multiplied by the number of lines, which would take hours each month, not to mention the risk of error. What to do to connect data between heterogeneous systems?
There Is No Api Everywhere
Internet is not an inter systems Such examples where people have to perform mechanical tasks, without any intelligence, with great repetitiveness, are innumerable. We created information processing systems to free up people’s time, but we haven’t finished the job at the borders, and for good reason, because we don’t know what’s on the other side, and that no one has standardized the way data is exchanged. Result: we pay hours and hours of people with BAC + 5 to copy and paste, or worse, recopy data by hand, because it is not possible to copy and paste in the input field. We finally have an internet, but at a low level: data
transmission. It’s already great! We do not yet have an “Intersystem” which would allow different information systems to exchange product sheets, orders, employee files, invoices, etc. The benefit of RPA: filling the gaps between systems This is where RPA comes in. RPA stands for Robotic Process Automation, process automation by robots. When interfaces are intended to be operated by people, RPA mimics the actions of people. And the best systems are able to adapt when fields are displayed in different places depending on the context, like a person looking with his eyes where the data they are looking
Internet Is Not An Inter Systems
for is on the page. The same goes for the input fields: RPA robots allow you to act like a human, and adapt according to the context, to enter a login, a password, retrieve a One Time Password received by SMS to connect to a service, go to the appropriate page, upload a file … RPA is the transposition at the level of a workstation of macros written in an application. And like a macro, robots can be robust, i.e. adapt to changes of contexts not necessarily all imagined, or be very fragile, and no longer work if we add a column or if the data that is normally displayed in the 3rd line of a web page is found in the 5th line .
A robot to copy and paste for me! RPA will live beyond the maturity of APIs We can say that RPA is a necessary evil to solve a temporary problem, and that standardization efforts will make it possible to converge from an Internet to an “intersytem”. For my part, I do not believe it, as long as we are dealing with human-machine interfaces and processes dealing with business data outside the scope of standardization. What I am putting in the field of standardization is data prescribed by regulations such as payroll or accounting data. The State has prescribed a way of coding the data for the payroll with the DSN