Input/output represents the robot’s input and output
But we chose this domain because it perfectly reflects the methodological approach needed to successfully face the robotization of a process: to think about what the input of the robot is and what will be its output.
Remember that the main objective of our Jidoka robots is to imitate human interaction with programs and applications in order to execute business processes and/or repetitive tasks based on a set of rules. To be able to execute this process we must tell the robot which set of information to apply to those tasks which would then free the human. Sometimes this entry is usually an Excel sheet with all the information to deal with, especially in massive actions, the robot may not need the Excel sheet provided by the human, rather it can go to look for it in some information system or database. In Jidoka, the entry information of a robot is what we call input.
Once this input is processed, the robot executes business rules that usually involve access, query, or even writing in other information systems, returning the result of everything it has executed in a format understandable by the user. Sometimes, especially in massive processes, the output is usually the same Excel input sheet, indicating, for each record whether the result of the operation has been correct (OK) or if the action could not be performed on that data (KO) and manual human intervention is therefore necessary .
Let’s take an example: One of the most robotic processes with Jidoka in BPO services is the closure of claims. After receiving a customer’s reclamation in a Call-Center, a series of actions are performed in the CRM and sometimes also in the ERP. At the end of all these tasks, the claim that originated them must be closed. In this case, the input is usually an Excel sheet with the list of claims obtained in the CRM, and the output is the Excel sheet itself indicating, for each claim whether the result is correct or whether there has been some problem in processing, which will require the action of a human agent.
Another example could be the robotization of the payment of payrolls in an SME carried out by our robot N0M1NA, where the input is the PDF file sent by the agency with all the payrolls of the employees, and the output is an email to each employee with their payroll, attaching only their file and indicating that the transfer has been made and that it will be credited to their current account after a couple of days.
Finally, this “.io” domain has become fashionable among startups in the United States.