ABBYY Timeline vs bupaR

ABBYY Timeline is a process intelligence platform for understanding and improving business processes. It supports discovery, analysis, monitoring, prediction, and simulation, combining process mining with task mining and desktop recording to connect user activity with process details. The platform reconstructs end-to-end processes as an interactive digital twin and includes over 25 pre-built analysis tools. It can analyze event data from databases, CSV files, spreadsheets, transaction logs, ERP systems, and message logs. Connections include SAP, Alteryx, FlexiCapture, and ODBC sources such as Oracle, Microsoft SQL Server, and PostgreSQL. Its API can connect third-party systems, upload data, retrieve process statistics, and embed Timeline features in other applications. Deployment options include cloud and self-hosted Windows or Linux systems. Security documentation describes encryption in transit and at rest, two-factor authentication, and role-based authorization. The 30-day trial offers unlimited access to the full range of features. Pricing is on request; there is no free plan.

bupaR is a free, open-source suite of R packages for working with business process data. It supports importing and preparing event data, calculating descriptive statistics, visualising processes, and checking conformance. Analysts can examine control flow, performance, and organisational aspects, while including custom process attributes in their workflow. It handles event logs, where each row represents an event, and activity logs, where each row represents an activity instance. Process maps help summarise processes and can be used in Shiny apps or exported to PDF, PNG, PS, or EPS. The bupaverse core contains bupaR, edeaR, eventdataR, processcheckR, and processmapR. The xesreadR package reads XES files from a local path or URL and writes event logs to XES. Installation instructions cover CRAN and GitHub development versions. The package requires R 3.5.0 or later and is licensed under MIT plus a license file. For prediction with processpredictR, Python, TensorFlow, and Keras are required. Validation of larger event logs can take time, though the documentation allows it to be disabled when the data meets requirements.