Event/log data is the transaction history of a specific order or case in one or more IT systems, simply put. Let’s explain it more with a simple example with a service order in a field service operations business.
Step 1, a service order is created in the IT system; this is logged in the IT systems as State=New with a unique order number (AA123) and a time stamp when it happen.
Step2, the order is assigned to an engineer; this is logged as State=Assigned with the same order number and a time stamp when it happened.
Step3, the work is done and the order is completed; this is logged as State=Completed with the same order number and a time stamp when it happened.
Step4, the order is invoiced to the client; this is logged as State=Invoiced with the same order number and a time stamp when it happened.
Step5, the invoice is paid and the order is closed; this is logged as State=Closed with the same order number and a time stamp when it happened.
On a technical level, this will give you log/event data that can be exported according to the format needed for AutoProcessDiscovery.com;
AA123; Assigned;2016-10-03 12:30
AA123; Completed;2016-10-04 18:45
AA123; Invoiced;2016-10-05 06:00
AA123; Closed;2016-10-15 14:38
This is only one, very simplified, example from one kind of business, however the principle is the same in all IT systems that involve work/tasks that are performed step by step (some kind of workflow), usually by different roles. If you are not sure how to get the data out, just ask your IT department or Service Desk or similar, they are definitely able to help you.
Then next step it to upload your data to AutoProcessDiscovery.com and your process will automatically be visualized for you. That will give you a great view on the actual true as-is process, and a perfect starting point for process and business development. Find your weakest link, and fix it.
Also if you need additional support we are more than happy to help you. Try us.