Monitoring and Explanation of Contract Execution: A Case Study in the Aerospace Domain

Felipe Meneguzzi, Sanjay Modgil, Nir Oren, Simon Miles, Michael Luck, Nora Faci, Camden Holt, Malcolm Smith

Research output: Chapter in Book/Report/Conference proceedingPublished conference contribution

2 Citations (Scopus)

Abstract

In the domain of aerospace aftermarkets, which often has long supply chains that feed into the maintenance of aircraft, contracts are used to establish agreements between aircraft operators and maintenance suppliers. However, violations at the bottom of the supply chain (part suppliers) can easily cascade to the top (aircraft operators), making it difficult to determine the source of the violation, and seek to address it. In this context, we have developed a global monitoring architecture that ensures the detection of norm violations and generates explanations for the origin of violations. In this paper, we describe the implementation and deployment of a global monitor in the aerospace domain of teJakob2008 and show how it generates explanations for violations within the maintenance supply chain. We show how these explanations can be used not only to detect violations at runtime, but also to uncover potential problems in contracts before their deployment, thus improving them.
Original languageEnglish
Title of host publicationProceedings of the International Joint Conference on Autonomous Agents and Multiagent Systems, AAMAS
Pages77-84
Number of pages8
Publication statusPublished - 2009
Externally publishedYes
EventProceedings of the 8th International Conference on Autonomous Agents and Multiagent Systems - Budapest, Hungary
Duration: 10 May 200915 May 2009

Conference

ConferenceProceedings of the 8th International Conference on Autonomous Agents and Multiagent Systems
Country/TerritoryHungary
CityBudapest
Period10/05/0915/05/09

Fingerprint

Dive into the research topics of 'Monitoring and Explanation of Contract Execution: A Case Study in the Aerospace Domain'. Together they form a unique fingerprint.

Cite this