European Commission logo
polski polski
CORDIS - Wyniki badań wspieranych przez UE
CORDIS
Zawartość zarchiwizowana w dniu 2024-05-27

Open System for inter-enterprise information Management in dynamic virtual envirOnmentS

Rezultaty

This result is a report that describes the likely benefits of adopting the OSMOS approach and defining the migration path (including organisational recommendations) to using the OSMOS approach, included in which is some further research that has been carried out in terms of the generalisation of the OSMOS approach to other industry sectors
The OSMOS Generic Virtual Enterprise Process Model constitutes the foundation of the OSMOS solution. It describes the operations of a Virtual Enterprise from its creation to its dismantlement. It takes into account the perspective of the three main stakeholders involved in a Virtual Enterprise, mainly: - The provider of a global Virtual Enterprise solution. - The provider of a Virtual Enterprise third-party plug-in service. - The user of a Virtual Enterprise solution. The main results of the OSMOS project are based on this work. This has currently a research and academic dimension, and will certainly be subject to adaptations, improvements and refinements in the near future as results of the exploitation of OSMOS.
The OSMOS API defines a set of API calls for both the High Level Security Service, the Information Management Service, the Service Manager Service and the message-based communication service. The OSMOS High Level Security API includes the following services: - The Actor Management Service deals with management of Actors, both Human and Entity. - The OSMOS Security Service provides "high-level" API calls, such as for management and checking of Default Access Rights. - The Project Management Service provides API calls for management of Projects on the server. - The Project Role Management Service provides API calls for the management of Project Roles on Projects on the server. The OSMOS Information Management Service API includes the following services: - The Cross Referencing Service deals with the handling of relationships between different Information Metadata objects. - The Information Metadata Service provides API calls that deal with the management of metadata about information held within a Project. - The Object Classification Service provides API calls for allowing projects to classify their own information (i.e. Information Metadata). - The Repository Management Service provides a set of API calls for the management of built-in file/document/object repositories on the Role A Server. The OSMOS Service Manager provides a number of API calls for managing the integration of Core and Third Party Services within the OSMOS Server.
This report gives a comprehensive description of the work carried out within the OSMOS (IST-1999-10491) project. The report first introduces the OSMOS project and gives the aims, objectives, methodology as well as the consortium composition. It gives then an overall description of the requirement capture work that was carried out using an action research based approach. The requirement capture methodology is presented, along with the process and information management practices of the end-users. The OSMOS Generic Virtual Enterprise Process Model, which constitutes the foundation of the OSMOS solution, is then described. This is followed by the presentation of the OSMOS conceptual solution. This includes the OSMOS models as well as the OSMOS API. The OSMOS system architecture is then presented as well as the reference tools implemented within the project (Role A Server Tool, VE Server Administration Tool, VE Project Administration Tool, and Web-based Information Browser). The project field trials as well as their evaluation are presented, followed by a formulation of business and process recommendations. Finally, lessons learnt and experiences acquired on the project are given at the end of the report, followed by description of future work in which the consortium members have embarked to further the dissemination and exploitation of the results.

Wyszukiwanie danych OpenAIRE...

Podczas wyszukiwania danych OpenAIRE wystąpił błąd

Brak wyników