Applying electronic contracting to the aerospace aftercare domain

https://doi.org/10.1016/j.engappai.2012.06.004Get rights and content

Abstract

The contract project was a European Commission project whose aim was to develop frameworks, components and tools to model, build, verify and monitor distributed electronic business systems based on electronic contracts. In this context, an electronic contract provides a specification of the expected behaviours of individual services, with the assumption that these services are often enacted by autonomous agents. Using the theoretical tools created by the project, in this paper we describe the complete life cycle of instantiating an electronic contracting system using the contract framework within the aerospace aftercare domain. Thus, we use a natural language description of parts of the types of contracts used in this domain to generate individual norms amenable to a computational representation, and how these norms are used to generate a concrete contract monitor. Moreover, we describe a concrete implementation of contract agents in the AgentSpeak(L) language and how these agents interact within a concrete instantiation of contract.

Introduction

As more and more business is conducted electronically over the internet, the need to guarantee transactions through formal electronic contracts is becoming increasingly important. In traditional business transactions, people need to meet and agree to terms of contracts before any exchange of goods and services takes place, but such a model is too slow, and inappropriate, in an interconnected world in which computer systems can replace human decision makers in closing deals and enacting decisions without constant supervision. In particular, systems of autonomous agents may be able to conduct business in an environment governed by formally documented norms, whereby different parties agree to the terms of business interactions specified in formal electronic contracts. These contracts must be represented in a way that allows autonomous agents to reason about them so that the agents can steer their behaviour towards compliance (Meneguzzi and Luck, 2009) and, more importantly, so that others can process such contracts and determine whether they have indeed been complied with.

To address this need, we have sought to create a framework, and guidelines, for the development of electronic contracting systems for real world applications. Like their physical counterparts, electronic contracts contain a set of clauses describing the expected behaviour of the signatories. In this view, clauses in such electronic contracts are comprised of individual norms (Oren et al., 2008) that describe expected agent behaviour in terms of the deontic modalities of obligations, prohibitions and permissions. For example, in the aerospace aftercare domain, aircraft engine manufacturers are contracted not only to sell new engines, but also to provide for their long term maintenance, subject to various terms by the airlines, and depending on terms from the suppliers of the component parts of these engines.

While we have previously outlined our basic computational framework for electronic contracting (Modgil et al., 2009), in this paper we review that framework and provide an instantiation of it for such an aerospace aftercare use case (Jakob et al., 2008), demonstrating the end-to-end application of the techniques developed, and how the generic framework can be used in a concrete real-world application of electronic contracting. The resulting application provides a representation of the required electronic contracts used in the multi-agent system that simulates the aftercare domain, as well as a monitoring process that is capable of generating explanations for contract violations (Modgil et al., 2009).

We start the paper by describing the domain in Section 2, including two specific scenarios in which electronic contracting is to be demonstrated. Next, we provide an overview of the contracting architecture in Section 3, explaining the components of an electronic contracting system following our framework. Once we have laid out the motivating aspects of our work, we proceed by describing the representation of the electronic contracts required for the aerospace domain in Section 4, showing how such contracts are represented originally in natural language, but eventually leading to the machine processable format needed in the system. After a contract has been created and signed by the relevant parties, we need to enact the contract, and monitor this enactment, as described in Section 5. The monitoring process detects when agents fail to comply with the norms they are committed to, but does not help to trace the original cause for a chain of violations, which may be critical in avoiding future failures. Hence, we describe a violation explanation mechanism in Section 6. We finish by showing the results of our practical implementation and empirical tests in Section 7.

Section snippets

Domain overview

The aerospace aftermarket is increasingly populated by customers buying a service rather than a product. For example, aircraft engine manufacturers provide long term commitments to make available operational engines for the aircraft of airlines (or operators) in order that their aircraft are not grounded while awaiting engines, and thus prevented from flying. Specifically, these commitments1

The CONTRACT architecture

The contract3 framework and architecture (Meneguzzi et al., 2008) allow electronic contracting technologies to be integrated into applications. This provides several benefits, as follows:

  • Explicit formulations of permissions, obligations and prohibitions on contract parties can be reasoned over and acted on by software agents to best meet business objectives.

Representing contracts

Electronic contracts are the central concept in the contract framework, thus making the representation of such contracts the vital element. In this section, therefore, we review our previous work on the specification of electronic contracts (Oren et al., 2008). At its most basic, an electronic contract is composed of a set of clauses, each of which contains a set of norms. Norms are essentially rules that can be categorised as permissions, obligations, and prohibitions, which respectively

Monitoring contracts

In this section, we build on the representation of Section 4, and review the contract monitoring framework (Faci et al., 2008, Modgil et al., 2009). Now, the goal of the monitoring framework is to be able to identify the status of a norm at any point in time. Typically, this status indicates whether a norm is abstract or instantiated, as well as whether it has been violated or expired. The ability to determine and reason about the status of a norm in this way is useful not only to agents

Explaining contract violations

Now that we have described the way in which the contract monitoring mechanism detects the current state of individual norms, we can proceed to describe how this monitoring mechanism can be extended to provide richer explanations as to the causes of particular norm states. We start by defining a basic explanation mechanism in Section 6.1, and then proceed to describe how more detailed explanations can be generated based on overlapping conditions of multiple norms in Section 6.2. Finally, we show

Implementation and experiments

To allow the evaluation of the contracting framework separately from the specific use case, we have divided the system into two main parts: the aftercare simulation and the contract-related functionality. The simulation part of our system implements a small subset of the aftercare scenario, including the scheduling of flights, update of engine usage information and engine maintenance operations. The contracting part of our system focuses on the communication and monitoring of requests by

Conclusions and related work

In this paper we have shown the practical applicability of the contract project framework by instantiating its architecture within an aerospace domain.9 Importantly, the domain was used throughout, to inform the development of the framework, being particularly suited to the application of contract technologies. We have described the components of the framework with a view towards practical implementation,

Acknowledgements

The research described in this paper was partly supported by the European Commission Framework 6 funded project contract (INFSO-IST-034418). The opinions expressed herein are those of the named authors only and should not be taken as necessarily representative of the opinion of the European Commission or contract project partners. The first author was partly supported by Coordenação de Aperfeiçoamento de Pessoal de Nível Superior (CAPES) of the Brazilian Ministry of Education.

References (23)

  • R.H. Bordini et al.

    Programming Multi-agent Systems in AgentSpeak using Jason

    (2007)
  • M.E. Bratman

    Intention, Plans and Practical Reason

    (1987)
  • M. Croitoru et al.

    Graphical norms via conceptual graphs

    Knowl. Based Syst.

    (2012)
  • M. d'Inverno et al.

    A formal specification of dMARS

  • Esteva, M., Rosell, B., Rodriguez-Aguilar, J.A., Arcos, J.L., 2004. Ameli: an agent-based middleware for electronic...
  • Faci, N., Modgil, S., Oren, N., Meneguzzi, F., Miles, S., Luck, M., 2008. Towards a monitoring framework for...
  • García-Camino, A., Rodríguez-Aguilar, J.A., Vasconcelos, W., 2007. A distributed architecture for norm management in...
  • J.F. Horty

    Agency and Deontic Logic

    (2001)
  • F.F. Ingrand et al.

    An architecture for real-time reasoning and system control

    IEEE Expert Knowl. Based Diagn. Process Eng.

    (1992)
  • Jakob, M., Pěchouček, M., Chábera, J., Miles, S., Luck, M., Oren, N., Kollingbaum, M., Holt, C., Vázquez, J., Storms,...
  • C. Krogh

    The rights of agents

  • Cited by (17)

    View all citing articles on Scopus
    View full text