Reactive scheduling using a multi-agent model: the SCEP framework

Multi-agent systems have been successfully applied to the scheduling problem for some time. However, their use often leads to poorly unsatisfactory disappointing results. A new multi-agent model, called supervisor, customers, environment, producers (SCEP), is suggested in this paper. This model, developed for all types of planning activities, introduces a dialogue between two communities of agents leading to a high level of co-operation. Its two main interests are the following: first it provides a more efficient control of the consequences generated by the local decisions than usual systems to each agent, then the adopted architecture and behaviour permit an easy co-operation between the different SCEP models, which can represent different production functions such as manufacturing, supply management, maintenance or different workshops. As a consequence, the SCEP model can be adapted to a great variety of scheduling/planning problems. This model is applied to the basic scheduling problem of flexible manufacturing systems, andit permits a natural co-habitation between infinite capacity scheduling processes, performedby the manufacturing orders, and finite capacity scheduling processes, performed by the machines. It also provides a framework in order to react to the disturbances occurring at different levels of the workshop

Open semantic service networks

Online service marketplaces will soon be part of the economy to scale the provision of specialized multi-party services through automation and standardization. Current research, such as the *-USDL service description language family, is already defining the basic building blocks to model the next generation of business services. Nonetheless, the developments being made do not target to interconnect services via service relationships. Without the concept of relationship, marketplaces will be seen as mere functional silos containing service descriptions. Yet, in real economies, all services are related and connected. Therefore, to address this gap we introduce the concept of open semantic service network (OSSN), concerned with the establishment of rich relationships between services. These networks will provide valuable knowledge on the global service economy, which can be exploited for many socio-economic and scientific purposes such as service network analysis, management, and control

Metamodel-based model conformance and multiview consistency checking

Model-driven development, using languages such as UML and BON, often makes use of multiple diagrams (e.g., class and sequence diagrams) when modeling systems. These diagrams, presenting different views of a system of interest, may be inconsistent. A metamodel provides a unifying framework in which to ensure and check consistency, while at the same time providing the means to distinguish between valid and invalid models, that is, conformance. Two formal specifications of the metamodel for an object-oriented modeling language are presented, and it is shown how to use these specifications for model conformance and multiview consistency checking. Comparisons are made in terms of completeness and the level of automation each provide for checking multiview consistency and model conformance. The lessons learned from applying formal techniques to the problems of metamodeling, model conformance, and multiview consistency checking are summarized

Embedded intelligence for electrical network operation and control

Integrating multiple types of intelligent, mulitagent data analysis within a smart grid can pave the way for flexible, extensible, and robust solutions to power network management

Study of application of space telescope science operations software for SIRTF use

The design and development of the Space Telescope Science Operations Ground System (ST SOGS) was evaluated to compile a history of lessons learned that would benefit NASA's Space Infrared Telescope Facility (SIRTF). Forty-nine specific recommendations resulted and were categorized as follows: (1) requirements: a discussion of the content, timeliness and proper allocation of the system and segment requirements and the resulting impact on SOGS development; (2) science instruments: a consideration of the impact of the Science Instrument design and data streams on SOGS software; and (3) contract phasing: an analysis of the impact of beginning the various ST program segments at different times. Approximately half of the software design and source code might be useable for SIRTF. Transportability of this software requires, at minimum, a compatible DEC VAX-based architecture and VMS operating system, system support software similar to that developed for SOGS, and continued evolution of the SIRTF operations concept and requirements such that they remain compatible with ST SOGS operation