Oct 2026· RSF Conference Series Engineering and Technology
Food Supply Chain Traceability
Abstract
Halal supply chain integrity in poultry slaughterhouses (Rumah Pemotongan Ayam, RPA) is often compromised by manual, fragmented record-keeping, which enables practices such as informally using another RPA's halal certificate. This study addresses a gap in existing halal traceability research, which has largely focused on technology selection (blockchain, RFID, QR code) without explicitly documenting the underlying business rules that operationalize halal-specific critical control points. Using a Design Science Research approach, this paper reports the problem identification, design and development, and demonstration stages for the BPMN-based business process design of "Sistem Jejak Halal," a QR code-based halal traceability system developed with a Type C RPA partner. Field observation, interviews, and focus group discussions were used to elicit halal control requirements, which were then modeled as four interrelated BPMN processes: RPA registration, breeder data management, JULEHA (Halal Slaughterer) data management, and halal QR code generation, and validated through iterative walkthroughs with the partner. The r esults show that BPMN can translate halal-specific risks, including certificate and Veterinary Control Number (NKV) validity and JULEHA (Halal Slaughterer) active-status verification, into explicit, auditable business rules embedded directly in the process design, rather than relying solely on the accuracy of consumer-facing information. This design provides an implementation-ready specification for the RPA partner and serves as the requirements basis for the subsequent Rapid Application Development phase of the broader research initiative. Findings are context-bound to a single Type C RPA case study; transferability to other medium-scale poultry slaughterhouses is proposed as future work.
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
It is proved that any global minimizer of the trajectory balance objective can define a policy that samples exactly from the target distribution, and empirically demonstrate the benefits of the trajectories balance objective for GFlowNet convergence, diversity of generated samples, and robustness to long action sequenc...
Esmeralda S. Whitammer, Moksh Jain, Emmanuel Bengio et al.· Neural Information Processin...· 302 citations· ⚡60
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 8, 2026
Jennifer Neville did not want to go into computer science—but that’s exactly where she landed. Neville discusses the starts and stops that led to her professional sweet spot and her work identifying “surprising failures” making it hard for AI to handle complexity. The post What AI gets wrong and what failure teaches us appeared first on Microsoft Research.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.