This template is designed for contributions to the International Conference on Process Mining (ICPM) Demo Track for Event Log Resources, based on the existing CEURART template with the necessary modifications. LINK TO THE WEBSITE: https://icpmconference.org/2027/call-for-demos/
\begin
Discover why over 30 million people worldwide trust Overleaf with their work.
%% The first command in your LaTeX source must be the \documentclass command.
%%
%% Options:
%% twocolumn : Two column layout. Do not use twocolumn for papers submitted to CEUR-WS!
%% hf: enable header and footer.
\documentclass[
% twocolumn,
% hf,
]{ceurart}
%%
%% One can fix some overfulls
\sloppy
\usepackage{float}
%%
%% Minted listings support
%% Need pygment <http://pygments.org/> <http://pypi.python.org/pypi/Pygments>
\usepackage{listings}
%% auto break lines
\lstset{breaklines=true}
%%
%% end of the preamble, start of the body of the document source.
\begin{document}
%%
%% Rights management information.
%% CC-BY is default license.
\copyrightyear{2027}
\copyrightclause{Copyright for this paper by its authors.
Use permitted under Creative Commons License Attribution 4.0
International (CC BY 4.0).}
%%
%% This command is for the conference information
\conference{ICPM 2027 Tool Demonstration Track, February 08-12, 2027, Rende, Italy}
%%
%% The "title" command
\title{[Dataset Name]: A Real-World Event Log for [Process/Domain]}
\tnotemark[1]
\tnotetext[1]{You can use this document as the template for preparing your
publication.}
%%
%% The "author" command and its associated commands are used to define
%% the authors and their affiliations.
\author[1]{Alice A. Andersen}[%
orcid=0000-0000-0000-0000,
email=andersen@uanywhere.eu,
]
\cormark[1]
\fnmark[1]
\address[1]{University of Anywhere,
University St. 42, 12345 Happyville, Country}
\author[2]{Bob B. Baron}[%
orcid=9999-9999-9999-9999,
email=b.baron@acme.com,
]
\fnmark[1]
\address[2]{ACME Inc., Profit St. 123, 12345 Happyville, Country}
\fnmark[1]
%% Footnotes
\cortext[1]{Corresponding author.}
\fntext[1]{These authors contributed equally.}
%%
%% The abstract is a short summary of the work to be presented in the
%% article.
\begin{abstract}
Here goes the abstract.
\end{abstract}
%%
%% Keywords. The author(s) should pick words that accurately describe
%% the work being presented. Separate the keywords with commas.
\begin{keywords}
Keyword \sep
Another keyword
\end{keywords}
%%
%% This command processes the author and affiliation and title
%% information and builds the first part of the formatted document.
\maketitle
%% Tool metadata table: if a metatadum is not applicable for your tool
%% (e.g., source code repository for a commercial application), write
%% N/A in the appropriate field
%% Please do not move/resize this table - as it should stay after the
%% abstract, before the first section - nor change the labels in the
%% metadata description column
%%
\begin{table*}[h]
\footnotesize
\centering
\begin{tabular}{p{0.30\textwidth}p{0.63\textwidth}}
\toprule
Metadata description & Value \\
\midrule
Dataset name & Dataset Name \\
Process \& domain & Process name and organisational domain \\
Log format & IEEE XES / OCEL 2.0 /... \\
Dataset size & MB / GB \\
Download URL & \url{URL} \\
Process reference model URL (in PDF) & \url{URL} \\
\bottomrule
\end{tabular}
\end{table*}
\section{Introduction}
Here goes the introduction. This is a citation \cite{katz2009research}.
\section{Provenance and Process Context}
A section describing the provenance and context of the dataset, the organisation and sector, the process, and the chosen case notion.
\section{Event Log Description}
A section describing the structure of the event log.
The section must include a table describing the event log schema. See an example description in Table~\ref{tab:schema}.
For OCEL 2.0 logs, include a description of all object types and relations.
\begin{table*}[h]
\footnotesize
\centering
\caption{Event-log schema}
\label{tab:schema}
\begin{tabular}{llllp{0.32\textwidth}}
\toprule
Attribute & Type & Unit & Domain & Meaning \\
\midrule
case:concept:name & String & -- & [domain] & Unique case identifier \\
concept:name & String & -- & [activities] & Activity label \\
time:timestamp & Timestamp & [timezone] & [date range] & Event timestamp \\
org:resource & String & -- & [resources] & Resource performing the event \\
{[attribute-1]} & {[type]} & {[unit]} & {[domain]} & {[Meaning]} \\
{[attribute-2]} & {[type]} & {[unit]} & {[domain]} & {[Meaning]} \\
\bottomrule
\end{tabular}
\end{table*}
This section must also contain a list or a table describing each activity label and explaining what the activity represents within the organization.
Finally, you need to include a table with a detailed summary of the event log. The mandatory table structure is presented in Table~\ref{tab:facts}. Make sure to include a summary of the missing-value rate by putting clear references to the log schema description.
\begin{table*}[h]
\footnotesize
\centering
\caption{Event data summary}
\label{tab:facts}
\begin{tabular}{llllp{0.32\textwidth}}
\toprule
Name & Value \\
\midrule
Number of events & [Num] \\
Number of cases & [Num] \\
Number of activities & [Num] \\
Number of resources & [Num] \\
Observation window & [Start date -- End date] \\
Median trace length & [Num] \\
Maximum trace length & [Num] \\
Case duration, 25th percentile & [Value] \\
Case duration, median & [Value] \\
Case duration, 75th percentile & [Value] \\
Case duration, 95th percentile & [Value] \\
Case duration, maximum & [Value] \\
Case attributes & [Num] \\
Event attributes & [Num] \\
\bottomrule
\end{tabular}
\end{table*}
\subsection{Known Artefacts and Preprocessing}
A sub-section describing the known data-quality issues and artefacts, including: migrations, batch-recorded events, changed labels, duplicates; what was cleaned, and what was deliberately left untouched.
\section{Business Questions}
A section describing three to six business questions a process owner would want answered, in the spirit of the BPI Challenges and phrased in the language of the organisation. For each: why it matters, what a satisfactory answer looks like, whether ground truth exists, and whether it is open or already answered. Questions endorsed by the data owner are strongly preferred.
\section{Conclusion}
Here goes the conclusion.
%%
%% The acknowledgments section is defined using the "acknowledgments" environment
%% (and NOT an unnumbered section). This ensures the proper
%% identification of the section in the article metadata, and the
%% consistent spelling of the heading.
\begin{acknowledgments}
This template makes use of the CEURART class, which belongs to CEUR-WS.
If needed, acknowledgements should go here.
\end{acknowledgments}
%% The declaration on generative AI comes in effect
%% in Janary 2025. See also
%% https://ceur-ws.org/GenAI/Policy.html
\section*{Declaration on Generative AI}
{\em Either:}\newline
The author(s) have not employed any Generative AI tools.
\newline
\noindent{\em Or (by using the activity taxonomy in ceur-ws.org/genai-tax.html):\newline}
During the preparation of this work, the author(s) used X-GPT-4 and Gramby in order to: Grammar and spelling check. Further, the author(s) used X-AI-IMG for figures 3 and 4 in order to: Generate images. After using these tool(s)/service(s), the author(s) reviewed and edited the content as needed and take(s) full responsibility for the publication’s content.
%%
%% Define the bibliography file to be used
\bibliography{sample-ceur}
\end{document}
%%
%% End of file