Data and process requirements for product recall coordination

Authors:
M. T. Wynn;C. Ouyang;A. H. M. ter Hofstede;C. J. Fidge
Affiliations:
Faculty of Science and Technology, Queensland University of Technology, GPO Box 2434, Brisbane, QLD 4001, Australia;Faculty of Science and Technology, Queensland University of Technology, GPO Box 2434, Brisbane, QLD 4001, Australia;Faculty of Science and Technology, Queensland University of Technology, GPO Box 2434, Brisbane, QLD 4001, Australia and Eindhoven University of Technology, Eindhoven, The Netherlands;Faculty of Science and Technology, Queensland University of Technology, GPO Box 2434, Brisbane, QLD 4001, Australia
Venue:
Computers in Industry
Year:
2011

Citing 5
Cited 0

Intelligent products: a step towards a more effective project delivery chain

Computers in Industry - Advanced web technologies for industrial applications
The Networked Physical World: An Automated Identification Architecture

WIAPP '01 Proceedings of the Second IEEE Workshop on Internet Applications (wiapp '01)
YAWL: yet another workflow language

Information Systems
Requirements on unique identifiers for managing product lifecycle information: comparison of alternative approaches

International Journal of Computer Integrated Manufacturing - Integrated Design of Product and Processes
Information Modeling and Relational Databases

Information Modeling and Relational Databases

Quantified Score

Hi-index	0.00

Visualization

Abstract

When an organisation becomes aware that one of its products may pose a safety risk to customers, it must take appropriate action as soon as possible or it can be held liable. The ability to automatically trace potentially dangerous goods through the supply chain would thus help organisations fulfil their legal obligations in a timely and effective manner. Furthermore, product recall legislation requires manufacturers to separately notify various government agencies, the health department and the public about recall incidents. This duplication of effort and paperwork can introduce errors and data inconsistencies. In this paper, we examine traceability and notification requirements in the product recall domain from two perspectives: the activities carried out during the manufacturing and recall processes and the data collected during the enactment of these processes. We then propose a workflow-based coordination framework to support these data and process requirements.