EP2297682A1

EP2297682A1 - Method for the traceability of data in a collaborative service-oriented workshop

Info

Publication number: EP2297682A1
Application number: EP09757688A
Authority: EP
Inventors: Bernard Marquez; Thierry Chevalier; Stefano Tursi
Original assignee: Airbus Operations SAS; Airbus Operations Ltd
Current assignee: Airbus Operations SAS; Airbus Operations Ltd
Priority date: 2008-05-14
Filing date: 2009-05-14
Publication date: 2011-03-23
Also published as: JP2011521340A; US20110066656A1; JP5524188B2; WO2009147312A1; FR2931275A1

Abstract

The invention particularly relates to a method for data management in a collaborative service-oriented workshop for processing objects associated with data representing actual data or processes. After selecting (230) at least one first object including at least one link, or a so-called first link, to a second object separate from said first object, at least one link to a third object, or a so-called second link, is accessed (240, 245), said second link being included in one of said first and second objects, said third object being separate from said first and second objects. A link is then established (245, 255) between the data associated with said third object and the other of said first and third objects.

Description

Method for data traceability in a collaborative service-oriented workshop

The present invention relates to computer architectures for collaborative work and more particularly to a method for traceability of data in a collaborative service-oriented workshop.

Optimizing the study and design phases of objects such as vehicles to reduce costs and development time usually requires the implementation of a specific IT environment.

For example, the aerodynamic study of an aircraft involves many specialists, working on different aspects of the same data, these aspects may or may not be related to each other. These specialists generally use different computer tools as well as different machines for the execution of the processes implemented. In addition, these specialists may be located, geographically, in separate locations.

It is therefore advantageous to implement an environment based on an open architecture for sharing data and computing resources, including computing resources. Such an environment should preferably accommodate a set of heterogeneous machines and operating systems.

It is also advantageous to use an interface allowing access to different different existing tools. Such a common interface must in particular be adapted to manage the data to be exchanged between these tools as well as to allow easy selection and access to the data.

In addition, the environment should preferably allow easy adaptation to future needs such as the integration of new tools, the management of new types of data and the generation of new types of results. In addition, there is a need for data traceability to determine the origin of the data produced and their life cycle during the various modifications and uses in computing or other processes. These problems are partially solved independently of each other.

For example, there are software applications such as SynfiniWay developed by Fujitsu (SynfiniWay and Fujitsu are trademarks) that allow the optimization of the execution of tasks in a heterogeneous environment. The SynfiniWay application can be used to virtualize global resources and present applications as services linked by sequences and data dependencies to automate IT processes.

There are also scripting languages such as Python and Java (Python and Java are trademarks) that can automate certain tasks and use existing tools. Python is a high-level, interpreted and object-oriented programming language. It can be used in many contexts and can be adapted to many uses with the help of specialized libraries. Data traceability is generally determined by the processes that led to the data. For example, in applications of PDM type (acronym for Product Data Management in English terminology), the user must follow predetermined processes without being able to derogate from them. The origin of a datum is thus determined by the process that made it possible to obtain the datum.

However, there is no centralized and optimized environment for the study and design of systems in a heterogeneous open collaborative environment.

The invention solves at least one of the problems discussed above.

The invention thus relates to a data management method in a collaborative service oriented workshop adapted to processing objects associated with data representative of actual data or processes, the method comprising the following steps,

selecting at least one first object comprising at least one link, called first link, to a second object, distinct from said first object; access to at least one link to a third object, called a second link, said second link being included in one of said first and second objects, said third object being distinct from said first and second objects; and,

establishing a link between the data associated with said third object and the other of said first and second objects. The method according to the invention thus makes it possible to manage data independently of their own characteristics such as their nature, their storage location and their size in order to allow global management thereof and make it possible to bind objects together and, thus, to offer the means to follow a close relationship between several objects. According to a particular embodiment, the data associated with said first object are representative of a process. Still according to a particular embodiment, the data associated with said second object are at least partially obtained from said process or said process is applied to at least a part of said data associated with said second object. Advantageously, the method further comprises a step of constructing a data tree according to said first and second links making it possible to establish a link between said first and third objects or between said second and third objects.

The steps of accessing at least one link and establishing a link are preferably recursively repeated to establish a link between data associated with at least two distinct objects.

According to a particular embodiment, at least one of said links contained in one of said objects is stored in a link table to facilitate the management of links and allow efficient construction of data trees.

Still according to a particular embodiment, said process uses at least one function external to said workshop oriented collaborative service to use existing functions and limit software development. The method according to the invention thus makes it possible to avoid maintaining several similar versions of software modules.

Still according to a particular embodiment, said objects are stored in a centralized database and said data associated with said objects are stored in remote devices to optimize the management of resources.

The invention also relates to a computer program comprising instructions adapted to the implementation of each of the steps of the method described above.

Other advantages, aims and features of the present invention will emerge from the detailed description which follows, given by way of non-limiting example, with reference to the accompanying drawings in which:

FIG. 1 schematically represents an exemplary architecture of a workspace for sharing data and resources according to the invention;

FIG. 2, comprising FIGS. 2a and 2b, illustrates a simplified block diagram of the data manager shown in FIG. 1 and an example algorithm for establishing a data tree, respectively;

FIG. 3 diagrammatically represents the functional elements of the execution engine illustrated in FIG. 1, as well as the information transmitted between these elements, for the execution of a process based on a Python type representation; FIG. 4 illustrates the collaborative service-oriented workshop according to the invention, from an application point of view, allowing execution of executable code resulting from external developments and specific developments;

FIG. 5 illustrates an example of encapsulation of an external ModelCenter model type function in a process model; FIG. 6 illustrates, in a synthetic manner, an example of an XML-type schema for the analysis of a stored process model in the form of an XML type description;

FIG. 7 illustrates an exemplary algorithm for executing unit processes of instantiated process models;

FIG. 8 illustrates an example of data processing that can be performed from a collaborative service-oriented workshop according to the invention; and,

FIG. 9 illustrates an exemplary device adapted to implement a part of the invention.

FIG. 1 schematically represents an example of an architecture 100 of a workspace for sharing data and resources according to the invention, also called a collaborative service-oriented workshop. As illustrated, this architecture is built around four main modules: the module 105 which is for access to data, the module 110 which is a data manager, the module 115 which is an execution engine and the module 120 which is about process management.

The data access module 105 is connected to the data management module 110 as well as to a centralized database 125, for example an Oracle type database (Oracle is a trademark). The data management module 110 is connected to the centralized database 125, to the execution engine 115 and to a set 130 representing distributed storage areas that can be organized in different ways, for example in the form of files or databases. of data. The execution engine 115 is itself connected to the set 130 of storage areas and the module 120 of process management.

Although this architecture is particularly suited to the design of complex objects such as aircraft, the following description is based on a simple example for the sake of clarity and brevity. This example is given for illustrative purposes.

The architecture 100 is adapted to manipulate computer objects representing data in the broad sense of the term, these data being able to be representative of a real object, for example an aircraft, or a process such as an aerodynamic drag calculation process. In a simplified way, the collaborative service oriented workshop works on data represented by computer objects based themselves on metadata that represent characteristic data.

The data, called framework data in English terminology or FD, are therefore physical data stored, for example, in the form of files in a storage area 130. These data characterize a real object, for example the mesh or the structure of the data. a chair, or a process, for example, the steps of a moving process. The size of this data is not limited, it can be several hundred megabytes. All used data can be stored in separate physical locations.

Objects, called framework objects in English terminology or FO, represent objects having a particular meaning to the application sense. As mentioned earlier, these objects are used to represent everything that can be manipulated by the collaborative service-oriented workshop. Objects are based on sets of metadata that can be understood as basic elements or characteristic elements. A set of metadata is thus associated with each object. Each type of metadata set can be associated with multiple objects. Qualifying a metadata set type allows you to form an object. If, for example, a type of meta-data set is associated with a chair, a qualification of the chair forming an object may be a chair.

For the sake of clarity, the computer implementations of objects, called framework object proxies in English terminology or FO proxies, are here assimilated to the objects themselves.

Among the objects are the instantiated process models, called instantiated process templates in English terminology or IPT. Instantiated process models are instances of process models, that is, process models applied to one or more FR2009 / 000569

objects. The process models, called process templates in English terminology or PT, are generic. For example, it is a process of building a living room from several chairs and a table, a process of renovating a house or a process of moving. Instantiated process models are represented as objects and can be manipulated as such in the Collaborative Service Oriented Workshop.

Meta-data, called meta-data framework in English terminology or FMD, correspond to particular information of the data. They make it possible to characterize data in order to facilitate their manipulation. Data can be associated with several sets of metadata. The meta-data are advantageously stored in the centralized database 125 in the form of tables or XML files (abbreviation of Extensible Markup Language in English terminology). A type is here associated with each set of metadata. The metadata includes generic information such as an identifier, a creation date and a creator name and specific information, specific to the associated data, for example the material, the color or the weight of a chair. The metadata also includes links to objects that include determining how the data was obtained and / or how it was used. These links make it possible to define data models, that is to say data trees.

The consistency of an object is verified through the links defined in the set of metadata associated with it. For example, a table data model can be determined such that a table is linked to a chair. If a table object is actually associated with a chair object, then the table object is said to consist of the meaning of the data model defined through its links.

The meta-data are for example described using an XML type language according to the structure presented in the appendix under the reference "code excerpt 1". 009/000569

The generic part of the metadata is common to all the data, so it is defined during the implementation of the collaborative service oriented workshop. Even if this part does not have a reason to be modified, its definition can evolve according to the needs. However, its evolution has an influence on all objects managed in the collaborative service-oriented workshop.

The specific part of the metadata is specific to each type of data and, therefore, to each type of metadata set. The definition of this part is done by the users of the collaborative service oriented workshop. The information of the specific part of the metadata is determined by the automatic extraction operations to be performed on the data.

Generic and specific metadata are advantageously used for searching and sorting data contained in the collaborative service-oriented workshop.

The example given in the appendix under the reference "code snippet 2" illustrates the XML type description of a type of metadata used to describe a chair.

As previously described, the metadata advantageously comprise a generic part and a specific part. The generic part includes, in particular, the following elements,

a key for managing access control to the data;

- a description of the type of object;

- a comment describing the data; - a creation date;

an identifier of the data which can be a key or a URL making it possible to access the data;

- a unique identifier of the data;

- information concerning the user who created the data; - the physical location of the data with its geographical location; and, 9 000569

- its status to know if a modification is in progress and by whom.

The second part of the metadata, specific to the object handled, here a chair, includes in this example the following attributes, - the number of feet;

- the thickness;

- the colour ;

- the material; and,

- the weight. The generic and specific parts can of course include other types of information.

The identifier or the address of a set of metadata makes it possible to find the data with which it is associated.

The qualification of a set of metadata representing a chair can be, in particular, "child" or "adult", to lead to two different objects.

In the same way, it is possible to define metadata and objects for tables. When importing an object defining a table, it is possible to define, at the level of a data model, that this object is only consistent if it is connected to at least one object of the chair type. Such a relationship between objects is defined by the links defined in the metadata. These links can also be represented in XML format or in a table. When importing a table type object, data model type links between the table type object and the chair type objects must be set in order to make this object consistent with the data model thus defined.

Alternatively, the metadata can be represented as tables. For example, a table can be associated with each type of data. The columns in the table represent metadata while each of its rows represents an object. Table 1 in the appendix illustrates a simplified example of representation of a type of set of metadata that can be associated with chair type data. It should be noted here that the links are not included in the table representing the R2009 / 000569

10

metadata. According to this example, the links are stored in a link table.

A link table can be represented, for example, in the form of the table given in the appendix under the reference table 2 where each column represents a pair of object identifiers between which a link is established.

Thus, the information stored in the metadata tables and in the link table makes it possible to manipulate all data, current and future, of the collaborative service-oriented workshop as well as to build data models. It may be noted here that the representation of the metadata in the form of tables is equivalent to an XML representation and that it is possible to use a conversion tool to switch from one representation to another.

The representation of the data characterizing physical objects or processes is thus carried out at several levels: - the raw data;

- metadata, which represent subsets of the raw data, extracted from them, that characterize the raw data;

- the objects, based on the metadata values, which are manipulated by the application modules; and,

- consistent objects that are objects related to other objects.

It should be noted here that according to this structure, it is not necessary to implement synchronization methods in the collaborative service-oriented workshop. The data access module 105 in particular enables a user to selectively and centrally access the meta-data stored in the centralized database 125 in order, in particular, to display these metadata, to produce views on these meta data. -Data allowing an efficient sorting of all the data accessible in the collaborative service workshop as well as, possibly, to follow the links uniting some of these data. The module 105 also makes it possible to record meta-data in the centralized database 125. It is thus possible for a user to enter meta-data through a human-machine interface (HMI) to specify information. which would not appear in the data stored in the storage areas 130. In order to access and save metadata, the user interface can use, in particular, queries of the SQL type (acronym for Structured Query Language in English terminology). ). This manual recording of meta-data is interesting for adding specific information that can not be extracted automatically from the data when importing the object into the workshop.

Similarly, the data access module 105 allows a user to selectively and centrally access the data stored in the storage areas 130 through the data management module 110 as well as to record data. To access and save data, the user interface advantageously uses APIs (acronym for Application Programming Interface in English terminology) specific and web services.

The data manager 110 is used as an interface between the data access module 105, the centralized database 125, the storage areas 130 and the execution engine 115 that is particularly adapted to applying processes to data. The data manager 110 also makes it possible to control the access rights of the users.

According to a particular embodiment, the data manager 110 is composed of a client part and a server part. The client part can be implemented in a Python language to allow access to the web services accessible in the server part. All standard data management functions such as import, export, publishing, collaboration and rights management are preferably available. This list is not exhaustive. The set of functions used during the life cycle of the data is available through this API

The server part can be implemented, for example, in Java or Python language to allow interfacing with the various databases of data and storage areas. This part also advantageously supports the mechanisms for extracting the meta-data from the data stored in the distributed storage areas 130 to the centralized database 125 containing the metadata. The execution engine 115 allows the execution of processes via process models based, for example, on business applications. An interface between the execution engine 115 and the storage areas 130 allows direct or API access to the data during the execution of the processes. The execution engine 115 is preferably linked to a calculation grid, for example of the SynfiniWay type, which manages the submission of the various processes on a distributed infrastructure as well as the displacement of the data during execution.

The execution engine 115 also preferably comprises an interface with applications using workflows in English terminology such as the ModelCenter (ModelCenter is a brand) or SynfiniWay applications, that is to say execution or task flow engines.

The process manager 120 enables the creation of high-level workflows, called composite processes, that encapsulate unit processes. These workflows can be the subject of parametric studies and parameter sensitivities and can be used to create behavior models. These functionalities can thus be used in multidisciplinary optimization studies.

Thus, the processing of non-unit processes, that is processes involving several different functions, is managed by the process manager to be, for example, broken down into unit processes which are then executed by the process engine. 'execution.

FIG. 2a is a simplified block diagram of the data manager 110. Using, for example, a file interface or a Corba type interface (acronym for Common Object Request Broker Architecture in 009/000569

13

Anglo-Saxon terminology, Corba is a trademark), data is created in the different databases (not shown).

A mechanism 200 for extraction, transformation and loading, called ETL (Abbreviation of Extract, Transform and Load in English terminology), is then implemented in order to extract the meta-data from the data stored in the data zones. storage 130. They are stored in the centralized database 125. This database thus collects the information of the physical data created in the various distributed storage areas 130. It should be noted here that the extraction mechanism is implemented. when the data is created, modified or deleted. It is specific to each type of data and metadata.

A qualification function 205 makes it possible to qualify the extracted metadata to form objects that can be stored in the centralized database 125. Following the qualification, a check is made on the consistency of the object. This consistency can be ensured through links stored with metadata or not, these links can be of different natures such as the version, the configuration, the data model and the user. A set of object links, defining a data model, can be used to determine links between multiple objects. Links are associated with metadata. As described above, they are stored with the latter or separately, for example in a link table stored in the centralized database 125. The links make it possible to establish later the traceability of the data, that is to say traceability between the different data produced or used during the execution of processes. There are several types of links, including the following,

- user links determined manually by the user between two data; R2009 / 000569

14

- model links to define a data model. These links are determined generically when creating a data model;

configuration links making it possible to establish a link between a set of objects to manage them in configuration, that is to say to allow the application of identical functions such as export, import and change of law;

- version links that make it possible to manage the same object according to different versions; and, - the production links that make it possible to establish an execution link between a set of objects. This type of link is created automatically during the data publication phase during or at the end of the execution of an instantiated process (IPT).

The set of these two-by-two links makes it possible to obtain the traceability carried by the data: the data contains all the histories, in particular as regards the executions of processes, the versions, the configurations, the users and the models.

It is thus possible to build complete trees of objects linked together by metadata and specific links. In the example of the chair and the table, a tree to know the metadata (color and location) of the table checks the data model linking it to the chairs having as metadata a specific color. Thus, step by step, it is possible to reconstruct complete trees for obtaining data.

It should be noted here that the data models, that is the data trees, are specific to the data handled in the collaborative service-oriented workshop. However, while data models can be derived from links between objects, they do not exist as such in the collaborative service-oriented workshop. They are implicitly created when defining objects, that is, sets of metadata corresponding to particular types of data.

As illustrated in FIG. 2a, a function 210 of the data manager 110 makes it possible to access the links and the objects to form a view of the consistent objects, i.e., a view showing the relationships between objects, which can be transmitted to a user as views of data models 215.

Similarly, the user can view objects and relationships as object views 220 and relationship views 230, such as lists.

Thus, according to this embodiment, the user, that is to say the client part of the data manager 110, has the following three types of views,

- a view through the metadata on the objects contained in the different databases;

a view of the data models created in the architecture 100; and,

- a view allowing to navigate between the different objects through links defined in the database of metadata, or associated with them, such as version links, user links, configuration links and links of production allowing traceability.

An XML type description of objects of the object proxy type, containing all the metadata associated with each data item, is advantageously created to be used, for example, by the execution engine 115 in order to access the data stored in the zones. storage 130 during the execution of processes.

FIG. 2b illustrates an example of an algorithm making it possible to establish a data tree from the objects manipulated in the collaborative service oriented workshop, these objects representing either real data or processes.

After having selected a first object (step 230), for example through a human-machine interface, a link to a second object, contained in this first object, is accessed (step 235). Next, a link to a third object, contained in this second object, is accessed (step 240) to enable a connection to be made between the first object and the third object (step 245) or between the data associated with the first object and those associated with the first object to the third object. Alternatively, a link to a third object, contained in the first object, is accessed (step 250) to make it possible to establish a link between the second object and the third object (step 255) or between the data associated with the second object and those associated with the second object to the third object. As suggested by the dotted arrow, these steps can be repeated, iteratively, to determine a data tree in which the sheets represent the data (or objects associated with the data) and the branches represent the links between the data ( or between the objects associated with the data). FIG. 3 diagrammatically represents the functional elements of the execution engine 115, illustrated in FIG. 1, as well as the information transmitted between these elements, for the execution of a process based on a Python representation. The execution engine 115 is activated by an object consisting of an instantiated process model 300 represented here as an XML type document.

The instantiated process model 300 is analyzed in an XML type parser 305, called XML parser in English terminology, to extract the information allowing the execution of the process. In particular, the parameters, the code and the data information necessary for the execution of the process are extracted from the XML document. Similarly, the data used by the process, forming the inputs of the process, are found using links on the objects concerned. All the information necessary to execute the process extracted from the XML document is transmitted to the kernel 310 of the execution engine.

The code of the instantiated process model 300, that is to say the data associated with the object representing the instantiated process model, corresponds to instructions directly executable by the execution engine, to instructions that are executable through a program. specific interface, such as Python type code, or functions or plug-ins called by the runtime engine such as ModelCenter functions. 00569

17

The execution of the process associated with the instantiated process model 300 may result in the creation of new objects 315, forming the output of the process. These objects are treated in the same way as the objects described above. In particular, metadata and links stored in the centralized database 125 as well as data stored in storage areas 130 are associated with these objects. Alternatively or in a complementary way, the input of the process can be modified during the execution thereof. The modified inputs forming an output of the process are called inputs / outputs. The kernel 310 of the runtime engine preferably uses an execution environment 320, also called the execution context of the instantiated process model. The execution environment is intended in particular to keep a history of the execution of the process (325), to make the data accessible in the format of the execution engine (330), for example in the form of objects of the type Python, monitor the execution of the process (335) and provide the interfaces 340 needed to run plug-ins to the runtime kernel.

When a process is executed and, in particular, when new objects are created, one or more links are automatically created in the metadata associated with the data used by the process (inputs, outputs and inputs / outputs) as well as in the metadata associated with the instantiated process model.

Before a process is run, the metadata associated with the instantiated process model includes references to the objects associated with the data to be used but not containing a link. Links are created in each object when the process is executed. For example, when a process uses data to produce a result, the following links are created during the execution of the process,

a link to the object associated with the process model is created in the object associated with the input data;

a link to the object associated with the input data is created in the object associated with the process model; a link to the object associated with the output data is created in the object associated with the process model; and,

a link to the object associated with the process model is created in the object associated with the output data. FIG. 4 illustrates an exemplary implementation of the collaborative service-oriented workshop according to the invention, from an application point of view, allowing the execution of executable code 400 resulting from external developments (405) and specific developments. (410). As shown, the execution of instantiated process models is recursive. Depending on the nature of the executable code and the implementation of the collaborative service-oriented workshop, the executable code is executed by the collaborative service-oriented workshop or by an external application. By way of illustration, the executable code is here executed by the collaborative service-oriented workshop if it is of Python type and by an external application if it is, for example, of the ModelCenter (MC) type.

Execution of functions external to the collaborative service-oriented workshop is carried out according to a mechanism for encapsulating external functions in process models. Figure 5 illustrates an example of encapsulation of a ModelCenter model in a process model. If the executable code is of Python type, the data needed to execute the code, including in particular the references to the input and output data and to the execution environment, are formatted according to the format Python (module 415). The process thus formatted is then encapsulated (module 420) in a process model that can be manipulated by the collaborative service oriented workshop as a standard object (module 425). As illustrated by the arrow between module 425 and module 415, the process model uses the Python interface when the process is to be executed.

Similarly, if the executable code is of ModelCenter type, the data necessary for the execution of the code, including in particular the references to the input and output data as well as to the execution environment, are encapsulated according to the ModelCenter format (module 430). The FR2009 / 000569

19

The formatted process is then encapsulated (module 435) in a process model that can be manipulated by the collaborative service-oriented workshop as a standard object (module 425). Again, as illustrated by the arrow connecting the module 425 to the module 430, the process model uses the adapted interface, here the ModelCenter interface, when the process has to be executed in order to allow the execution of the process outside. of the workshop oriented collaborative service.

As suggested by reference 460, other formats can be used. The instantiation of the process model can be carried out after encapsulation of the process by means of a man-machine interface, that is to say here between the modules 420 and 425 and between the modules 435 and 425.

One of the purposes of encapsulation is to adapt the process models according to a predetermined format. In particular, encapsulation makes it possible to check the validity of the data, to determine the necessary parameters and to impose default values on the missing parameters and to copy and / or generate the appropriate code. Optionally, encapsulation also makes it possible to define execution directives, that is to say to define, for example, which machines are to be executed on the processes or parts of the processes.

Encapsulation of external functions in a process model is preferably performed using the following XML sections,

- inputs and outputs: links to the objects associated with the data managed in the collaborative workshop allowing their use in external functions;

- parameters: parameters used by external functions; and,

- code: call to the external function.

Figure 5 illustrates an example of encapsulation of a model

ModelCenter 500 in a 505 process model. As shown, a link is established between each section of the process model and the corresponding fields of the ModelCenter model. The call to the executable code of the model ModelCenter is here carried out through a Python script 510. For example, a process model can use a function external to the collaborative service-oriented workshop. Due to the structure of the objects associated with the process models and in particular the links, a traceability of the data used in input or output of process models using external functions is possible.

Similarly, it is also possible to encapsulate process models in external functions, for example in ModelCenter models. Thus, process models developed in the collaborative service-oriented workshop can be directly used by external applications. Via this mechanism, it is possible to use and link process models to other external functions while maintaining, at runtime, the use of managed data in the collaborative service-oriented workshop as well as the traceability associated.

The execution of process models from an external application is performed by the SRW neutral integration layer of the integration layer of the collaborative service-oriented workshop, called SRUN, used to execute the instantiated process models.

A process model can encapsulate external functions and can be encapsulated in external functions. In this double encapsulation mechanism, the degree of traceability of the data is thus determined by the functions performed by the collaborative service-oriented workshop and by external applications.

As an illustration, if a process model A of the collaborative service-oriented workshop uses functions B, C and D, B and C are process models of the collaborative service-oriented workshop and D is a model. ModelCenter itself makes use of E and F functions, E being an external function and F being an encapsulated process model of the collaborative service oriented workshop, it is possible to follow the links between B, C and D but not between E and F (simply between the input of E and the output of F), executed outside the collaborative service-oriented workshop. It is thus possible to determine the level of granularity desired for the traceability of the data. As indicated above, the data associated with the objects characterizing instantiated process models can be represented in the form of files, for example in the form of an XML type file. The descriptions of the process models advantageously comprise several sections, specific to each type of information.

Process models can themselves be composed of process sub-models that can be stored in sections of process models. The process sub-models are here references to process models accessible in the collaborative service-oriented workshop. Thus, it is possible to create composite process models that refer to several unit process models or themselves composite.

The attributes of an instantiated process model are for example the following: the version of the XML schema for extracting the information from the process model;

- the identifier, name, version and type of the process model;

the identifier of the instantiated process model;

- the ModelCenter execution identifier if the instantiated process model refers to a ModelCenter type function;

the paths to the mechanisms allowing the execution of the process in a secure manner (called sandboxes in English terminology);

- the execution state of the process model that specifies in which execution state is the instantiated process model, for example submitted, running, executed successfully or executed with error;

the state of the process model defining its internal state, for example primary, partially instantiated, instantiated, running or executed; and, - comments.

The section on inputs, outputs, inputs / outputs and parameters of an instantiated process model includes for example the name, type and category. Other information can be associated with the inputs, outputs, inputs / outputs and parameters of an instantiated process model such as the type of user involved, a description and help. One section is used for each input, output, input / output and parameter.

The runtime context section of an instantiated process model includes a classification section that specifies the tools used during the execution of the instantiated process model. The execution context section of an instantiated process model also includes a context creation section for storing the execution context of the instantiated process model and a current execution context section specifying the configuration. to be used to execute the process and to store the choices made by the compute grid controller. The execution context section of an instantiated process model may also include an execution server section to specify the configuration of the calculation grid chosen during instantiation of the process model as well as a section of the execution model. execution report completed at the end of the execution of the process containing for example an error code or the business information relating to the execution of the process. The attributes of the context creation section and the current execution context section are, for example, the following,

- the name and type of the machine used to execute the process and its type of operating system; and,

- the date of creation of the context or execution of the process. The data section of an instantiated process model is intended to store process model private data available during process execution. This section may itself include sections such as sections specific to particular processes such as ModelCenter processes. The code section of an instantiated process model includes the code of the process to be executed. The attributes of this section are for example the language used such as the Python language, the version of the code and, possibly, comments.

An instantiated process model may further include a description of the list of available servers and / or preferred servers for executing the process.

FIG. 6 is a synthetic illustration of an XML schema example 600 for the analysis of a process model stored as an XML type description. The XML 600 type schema describes the different sections contained in a file representing a process model as well as the links to the XML type sections of the data management and process management parts.

The links shown in solid bold represent the inclusion, the dashed lines represent the notion of import and the dashed lines represent the notion of implicit import. Process Template (PT) extensions are associated with process models, ie the runtime engine, DM (Data Management) type extensions are associated with the data, that is to say to the data manager, and the MC type extensions are associated with ModelCenter, that is, a particular process manager. As illustrated, a process model 605 includes several subsets 610 to 640 corresponding here to the sections of the inputs, outputs, parameters, servers, execution context, data and code, respectively. The input, output, and parameter sections themselves include 645 arguments. The process model implicitly includes information about the specific 650-1 to 650-n models such as EDMG models (Model Editor acronym Generalized), ModelCenter and Excel (Excel is a brand). The ModelCenter model of the process model receives information from a particular model 655. Note here that the Excel model uses a reference to the function to be used, for example a URL (acronym for Uniform Resource 9 000569

24

Locator in English terminology) while ModelCenter is, because of encapsulation, included in the process model.

The data specified in sections 610, 615 and 620 are derived from objects 660 which themselves include links (665 and 670) to other objects.

Thus, the references 600 to 650 are associated with the generic process model while the set of references corresponds to an instantiated process model. It should however be noted here that the parameters 520 can also be manually modified by the user. FIG. 7 illustrates an exemplary algorithm 700 for executing unit processes of instantiated process models.

The instantiated process model 705 is first analyzed (step 710) to check its validity using a predetermined XML scheme 715. If it is not valid, the execution of the process is stopped and a another model of instantiated process can be processed. If the instantiated process model is valid, the information contained in this model is extracted (step 720).

The extraction of the information makes it possible in particular to determine the configuration of the execution context 725 as well as the execution environment 730 which can notably comprise the inputs, the outputs, the inputs / outputs, the parameters and / or the data specific to the model. instantiated process. According to a preferred embodiment, the configuration of the execution context 725 and the execution environment are determined according to the Python format. The configuration of the execution context is then controlled according to the validity of the execution domain (step 735). Indeed, the creator of a process has the possibility of specifying a domain of validity, for example a specific version of software. If a user wants to use another version, he can be alerted or forced to change his choice, as the validity condition of the execution domain is not satisfied. If the configuration is not valid, the execution of the process is stopped and another instantiated process model can be processed. If the configuration is valid, the conditions on the inputs and the inputs / outputs are checked (step 740). When instantiating the process, the user may have referenced an object that can not be used in this process because it does not meet the conditions set by the process creator. In the example given with regard to the table and the chair, the process of moving may, for example, have as a condition a specific color of the chair. If the user chooses a chair of another color, the moving process can not take place. If the conditions on the inputs and the inputs / outputs are not valid, the execution of the process is stopped and another model of instantiated process can be processed.

If the conditions on the inputs and the inputs / outputs are valid, the execution of the process is implemented according to the code of the instantiated process model (step 745), that is to say according to the data associated with the object representing the instantiated process model. The code of the instantiated process model is then executed

(step 750). In general, the kernel of the execution module, called SRUN ₁ loads in memory the inputs, the inputs / outputs as well as the Python modules necessary to execute the code. If necessary, a distributed runtime environment, based on the capabilities of the SRUN runtime, can be implemented.

In the case of composite instantiated process models, the SRUN execution module creates instances of the process sub-models in memory and executes them successively as unit instantiated process models. The consistency between the different unit processes is then ensured by the execution engine of the workflow or workflow.

During the execution of the process, the script containing the code is executed in the corresponding execution environment, possibly on a machine different from that of the data manager, according to the choice of the manager of the calculation grid. Preferably, the mechanisms for executing the process in a secure manner are used to read and write the physical data, to memorize the history of the execution of the process and for the temporary storage of the data.

After the execution of the script, that is, the process, the execution engine passes the outputs to the appropriate domain and stores the execution report.

FIG. 8 illustrates an example of data processing 800 that can be performed in a collaborative service-oriented workshop according to the invention. In this example, 805 data is information about a ruined house. An object, referring to meta-data, is associated with these data, indicating the state in ruin as well as other information deemed relevant, here the number of pieces and the number of windows. Data 810 corresponds to information about a habitable house. Again, an object, referring to metadata, is associated with these data, specifying a state, here habitable status, as well as information deemed relevant, that is to say here the number of pieces and the number of windows. The data 810 can be obtained from the data-bound object 805, and hence from the data 805, using an object representing an instantiated renovation process template 815.

Similarly, the object corresponding to the data 810 can be combined with a data-related dining room object 820 and a data-related bed object 825 in an instanciated moving process model 830 to create an object 835. Data-related metadata 835 specifies here the lived status as well as the number of rooms and windows. The example given in the appendix under the reference "code snippet 3" illustrates a simplified example of meta-data associated with the data 805 of FIG. 8 before the execution of the renovation process.

As shown in this example, the meta-data includes generic information, including the type and name of the object as well as the link to access the corresponding data, and specific information, here the state, the number of windows and the number of pieces. It should be noted that the metadata are of the IN type, that is, they do not correspond to data created by an instantiated process model.

The renovation process model that can be used to process the previous example representing a ruined house can be described generically as presented in the appendix under the reference "code snippet 4".

This process model takes a home-type object as input and outputs another home-type object. This process model can be instantiated to contain, in particular, references to the objects associated with the data 805 and 810 of FIG. 8. The instantiated process model is then, for example, that given in the appendix under the reference "code extract 5". ".

As indicated, the instantiated process model further includes execution parameters, the identification of the execution machine, the application configuration used as well as the execution history links between the objects associated with the data 805 and the instantiated process model 815 and between the objects associated with the instantiated process model 815 and the data 810.

After executing the process corresponding to this instantiated process model, the metadata related to the data 805 is modified to add a history link allowing the traceability of the data. The meta-data associated with the data 805 can therefore, after the execution of the process, be represented in the manner given in the appendix under the reference "code snippet 6".

As explained in this example, a link has been created between the objects associated with the data 805 and the instantiated process model 815. Thus, using the object associated with the instantiated process model 815, it is possible to establish a link between the objects associated with the 805 and 810 data.

Similarly, after execution of the process, the data 810 as well as the metadata associated therewith, including the links, are created. The meta-data associated with the data 810 can then be represented in the manner given in the appendix under the reference "code extract 7". As before, a link has been created between the object associated with the data 810 and the object associated with the instantiated process model 815. Thus, using the object associated with the instantiated process model 815, it is possible to establish the link between the data 805 and 810. It should be noted that the meta-data here are of the OUT type, that is, they correspond to data created by an instantiated process model in the 'workshop oriented collaborative service.

Similarly, a second process model can be created and instantiated to process the data 810, 820 and 825 to create the data 835 and the associated object. When the second instantiated process model 830 characterizing a moving process is executed, the meta-data associated with the data 810 is modified to integrate the link induced by the execution of the instantiated process model 830. The meta-data associated with the data 810 may then be expressed in the form given in the annex under the reference "code excerpt 8".

The link created between the object associated with the data 810 and the object associated with the instantiated process model 830 makes it possible, using this object, to establish the link between the objects associated with the data 810 and 835.

On the other hand, when executing the second instantiated process model 830, the data 835 is created along with the associated object. The associated metadata can be represented in the form given in the appendix under the reference "code snippet 9".

The link created between the object associated with the data 835 and the object associated with the instantiated process model 830 makes it possible, using this object, to determine the links between the objects associated with the data 835 and 810, between the associated objects. data 835 and 820 and between objects associated with data 835 and 825.

A device adapted to implement a part of the invention is illustrated in Figure 9. The device 900 is for example a microcomputer, a computer or a workstation.

The device 900 here comprises a communication bus 902 to which are connected: a central processing unit or microprocessor 903 (CPU, acronym for Central Processing Unit in English terminology);

a read-only memory 904 (ROM, acronym for Read OnYy Memory in English terminology) that may include the programs "Prog", "Prog1" and "Prog2";

a random access memory or cache memory 906 (RAM, acronym for Random Access Memory in English terminology) comprising registers adapted to record variables and parameters created and modified during the execution of the aforementioned programs; and, a communication interface 918 adapted to transmit and receive data.

Optionally, the device 900 can also have:

a screen 908 making it possible to display data and / or to act as a graphical interface with the user who can interact with the programs according to the invention, using a keyboard and a mouse 910 or another pointing device, a touch screen or a remote control;

a hard disk 912 which may comprise the aforementioned "Prog", "Progi" and "Prog2" programs and data processed or to be processed according to the invention; and, a memory card reader 914 adapted to receive a memory card 916 and to read or write to it data treated or to be processed according to the invention.

The communication bus allows communication and interoperability between the various elements included in the device 900 or connected to it. The representation of the bus is not limiting and, in particular, the central unit is capable of communicating instructions to any element of the device 900 directly or via another element of the device.

900.

The executable code of each program enabling the programmable device to implement the processes according to the invention can be stored, for example, in the hard disk 912 or in the read-only memory 904. 009/000569

30

According to one variant, the memory card 916 may contain data as well as the executable code of the aforementioned programs which, once read by the device 900, will be stored in the hard disk 912.

According to another variant, the executable code of the programs may be received, at least partially, through the interface 918, to be stored in the same manner as described above.

More generally, the program or programs may be loaded into one of the storage means of the device 900 before being executed. The central unit 903 will control and direct the execution of the instructions or portions of software code of the program or programs according to the invention, instructions which are stored in the hard disk 912 or in the read-only memory 904 or else in the other elements of aforementioned storage. When powering on, the program or programs that are stored in a non-volatile memory, for example the hard disk 912 or the read-only memory 904, are transferred into the random access memory 906 which then contains the executable code of at least one part of the program or programs according to the invention, as well as registers for storing the variables and parameters necessary for the implementation of the invention. Naturally, to meet specific needs, a person skilled in the field of the invention may apply modifications in the foregoing description.

ANNEX

Code excerpt 1:

<Workshop.DM:FrameworkMetaData> <Workshop. DM: Attributes. Generic f>

<Atelier.DM:Attributes. Specifies /> </Atelier.DM:FrameworkMetaData>

Code snippet 2: <Workshop.DM:FrameworkMetaData xmlns: Workshop.DM = "http://www.societe.com/egai/Atelier/DM">

<Atelier.DM:Attributes. Generic acl_name = "Private" comments = "None" creation_date = "2006-04-27 10:29:43" dbJype≈ΕLEMENT "externaljd =" chair_number_0010100432325 "id =" 1411 "lock_owner =" None "lock_state =" 0 "mdb_instance = "MDB_exploit" modification_date = "2006-04-27 10:29:43" name = "chair1" owner = "name_office" publication_level = "Prive" shared_state = "None" site = "Toulouse" source = "LOCAL" status = "Prive" version_comments = "None" version_number = "None" version_owner = "None" version_state = "None" version _tag = "None" />

<Aielier.DM:Attributes.Specific nb_foot = "4" thickness = "5cm" color = "red" material = "wood" weight = "2kg" />

</Atelier.DM:FrameworkMetaData>

Code snippet 3:

<Workshop.DM:EEObjectProxy xmlns: Workshop.DM = "http://www.societe.com/egat/Atelier/DM" publish = "0" state = "O" type = "IN"> <Workshop. DM: OriginalPointer>

<Workshop.DM:Pointer external_id = "description for access to physical data" /> </Atelier.DM:OriginalPointer> <Workshop.DM:ObjectProxytype= "HOUSE"> <Workshop.DM:Pointer external_id = "description for access to the physical data "/>

<Workshop.DM:FrameworkMetaData xmlns: Workshop.DM = "http://www.societe.com/egat/Atelier/DM">

<Workshop. DM: Attributes. Generic acl_name = "Prive" db_type = "HOUSE" external_id = "descήption for access to physical data" id = "login" mdbJnstance = "MDB_exploit" modification_date = "" name = "my blue home" source = "CMSDK" status = "Private" />

<Workshop.DM:Attributes.Specific state = "ruined" nb_window = "4" nb__pieces = "10" /> </Workshop.DM:FrameworkMetaData> </ 'Workshop. DM: ObjectProxy> </Atelier.DM:EEObjectProxy>

Code excerpt 4:

<? xml version = "1.0"?>

<Atelier.PT:ProcessTemplate comment≈ "my first treatment" creator = "creator" id = "login" name = "Home Renovation" schemaVersion = "0.1" state = "primary" execution_state = "not_submitied" type = "action" version = "0.1" xmlns: Workshop. DM = "http: // www.company.com/egat/Workshop/DM" xmlns: Workshop.MC = "http://www.societe.com/egat/Atelier/MC" xmlns: Atelier.PT = "http : //www.societe.com/egat/Atelier/PT "xmlns: xsi =" http://www.w3.org/2001/XMLSchema-instance " 69

32

xsi: schemaLocation = "http://www.societe.com/egat/Atelier/PT Atelier.PT.ProcessTemplate.xsd http://www.societe.com/egat/Atelier/DMAtelier.DM.xsd">

<Atelier.PT:SandboxPointer externaljd≈ "" source_name = "" source__site = "" source_type = "" type = "" /> <Workshop.PT:lnput categorγ = "object" desc = "house in ruins" name = "" type = "HOME">

<Atelier.PT:Condition>

<! [CDATA [number of windows> 3]]> </ Workshop.PT:Condition> </ Workshop.PT:lnput> <Workshop.PT:Output category = "object" desc = "habitable house" name = "" type = "HOME">

</ Workshop. PT: Output>

<Atelier.PT:Parameter desc = "runtime parameters" name = "para_list" type = "list" /> <Workshop.PT:Server>

<Atelier.PT: ValidServer> <! [CDATA [keyword and values describing the machine characteristics]]>

</ Workshop.PT:ValidServer> <Workshop.PT:DefaultServer>

<! [CDATA [keyword and characteristic values of the default machine]]> </ Workshop. PT: DefaultServer> </Atelier.PT:Server>

<Atelier.PT:ExecutionContext>

<Workshop.PT:Classification processType = "batch"> <Workshop.PT:Suite name = "Suite1" /> <Workshop.PT:Tool name = "Tool1" /> </Workshop.PT:Classification>

<Atelier.PT:CreationContext class≈ "" date = "" hostname = "" osname≈ "" type = "">

<! [CDATA [[configuration] keyword and value describing the default application configuration

[validity] condition of validity of the application configuration]]> </Atelier.PT:CreationContext>

</Atelier.PT:ExecutionContext> <Atelier.PT:Data/> <Atelier.PT:Code comment = "comment on the code" language = "python" version = "">

<! [CDATA [Code to execute]]> </ Workshop.PT:Code>

</ Workshop. PT.Process Template>

Code excerpt 5:

<? xml version = "1.0"?> <Workshop.PT:ProcessTemplate comment = "my first treatment" creator = "creator" id = "login" name- "Home Renovation" schemaVersion = "0.1" state = "primary" execution_state = "not_submitted" type = "action" version = "0.1" xmlns: Workshop.DM = "http: // www. societe.com/egat/Atelier/DM "xmlns: Workshop MC =" http: // www. society. com / egat / Atelier / MC "xmlns: Atelier.PT =" http://www.societe.com/egat/Atelier/PT "xmlns: xsi =" http: // www. w3.org/2001/XMLSchema- instance "xsi: schemaLocation =" http: // www. societe.com/egat/Atelier/PT Atelier.PT.ProcessTemplate.xsd http://www.societe.com/egat/Atelier/DM Atelier.DM.xsd ">

<Atelier.PT:SandboxPointer external_id = "" source_name = "" /> <Workshop.PT:lnput category = "object" desc = "ruined house" name = "Data_805" type = "HOUSE">

<Workshop. PT: Condition>

<! [CDATA [number of windows> 3]]> </ Workshop.PT:Condiiion> <Workshop.DM:EEObjectProxy publish≈'O "state≈'O" type = "IN">

<Workshop. DM: OήginalPointer> <Atelier.DM:Pointer externaljd = "description for access to physical data"/>

</Atelier.DM:OήginalPointer> <Workshop.DM:ObjectProxy type = "MAISθN"> <Workshop.DM:Pointer externaljd = "description for access to physical data" />

<Workshop. DM: FrameworkMetaData xmlns: Workshop.DM = "http://www.societe.com/egat/Atelier/DM">

<Atelier.DM:Attributes. Generic acl_name = "Prive" db_type = "HOUSE" external_id = "description for access to physical data" id = "login" mdb_instance = "MDB_exploit" modification_date = "" name = "my blue home" source = "CMSDK" status = "Private" />

<Workshop.DM:Attributes.Speçific state = "ruined" nb_window = "4" nb_pieces = "10" /> <Workshop.DM:Links>

<Workshop.DM:Link comments = "description of the link" date≈ "" id__FO_1 = "identifier given 805" id_FO_2 = "identifier IPT 815" mdb_instance = "MDB_exploit" owner = "to39751" subtype = "subtype of link" type = "HISTORY" xmlns: Workshop.DM = "http://www.societe.com/egat/Atelier/DM" /> </Atelier.DM:Links>

</ Workshop.DM:FrameworkMetaData> </ Workshop. DM: ObjectProxy> </ Workshop. DM: EEObjectProxy> </Atelier.PT:lnput> <Workshop.PT:Output category = "object" desc = "habitable house" name = "Data_810" type = "HOUSE">

<Workshop.DM:EEObjectProxy publish = "1" state = "1" type = "OUT"> <Workshop. DM: SandboxPointer>

<Workshop.DM:Pointer external_id = "description to access the sandbox" sourcejname≈ "" source_site = "" source_type = "" type = "" /> </ Workshop. DM: SandboxPointer> <Workshop.DM:FinalPointer>

<Atelier.DM:Pointer external_id = "description for access to the physical data" /> </Atelier.DM:FinalPointer>

<Workshop.DM:ObjectProxy type = "HOUSE">

<Atelier.DM:Pointer external_id = "description for access to the physical data" />

<Workshop. DM: FrameworkMetaData xmlns: Workshop. DM = "http: // www.company.Com / egat / Workshop / DM">

<Atelier.DM:Attributes. Generic acl_name = "Prive" db_type = "HOUSE" externaljd = "descήption for access to the physical data" id = "identifier" mdbJnstance = "MDB_exploit" modification_date = "" name = "my blue house" source = "CMSDK" status = "Private" /> <Workshop.DM:Attributes.Specific eiat = "livable" nb_window = "6" nb_pieces = "12" />

<Atelier.DM:Links>

<Workshop.DM:Link comments = "link deletion" date = "" id_FO_1 ^ 'IPT identifier 815 "id_FO_2 =" identifier Data 810 "mdbJnstance =" MDB_exploit "owner =" to39751 "subtype =" subtype of link "type ≈ΗISTORY "xmlns: Workshop.DM =" http://www.societe.com/egat/Atelier/DM "/>

</ Workshop. DM: ϋnks> </ Workshop.DM:FrameworkMetaData> </ Workshop. DM: Ob] ectProxy> </ Workshop. DM: EEObjectProxy>

</Atelier.PT:Output>

<Atelier.PT:Parameter desc- "execution parameters" name = "parajist" type = "list"><Atelier.PT:ParameterValue> <! [CDATA [runtime parameter]]></Aielier.PT:ParameterValue></Atelier.PT:Parameter><Workshop.PT:Server><Workshop.PT:ValidServer>

<! [CDATA [keyword and values describing machine characteristics]]> </Atelier.PT:ValidServer> <Atelier.PT:DefaultServer>

<! [CDATA [keyword and characteristic values of the default machine]]> </Atelier.PT:DefaultServer>

</Atelier.PT:Server> <Workshop.PT:ExecutionContext>

<Atelier.PT:Classification processType = "batch">

<Atelier.PT:Suite name = "Suite1" /> <Workshop.PT:Tool name≈ "Tool1" />

</Atelier.PT:Classification> <Atelier.PT:CreationContext class = "" date = "" hostname = "" osname- '"type =" ">

<! [CDATA [[configuration] keyword and value describing the default application configuration [validity] condition of validity of the application configuration]]>

</Atelier.PT:CreationContext> <Atelier.PT:RunContext class = "" date = "" hostname = "" osname = "" type - "">

<! [CDATA [[configuration] keyword and value describing the application configuration used]]> </Atelier.PT:RunContext>

<Atelier.PT:RunServer>

<! [CDATA [keyword and value describing the runtime machine used]]> </Atelier.PT:RunServer> <Workshop.PT:ExecutionReport return_code = "0"> <! [CDATA [Runtime Report]]>

</Atelier.PT:ExecutionReport> </Atelier.PT:ExecutionContext> <Workshop.PT:Data />

<Workshop.PT:Code comment = "comment on the code" language = "python" version = ""> <! [CDA TAl Code to execute]]>

</Atelier.PT:Code>

</Atelier.PT:ProcessTemplate>

Code snippet 6: <Workshop.DM:EEOhjectProxy xmlns: Workshop.DM = "http://www.society.com/egat/Atelier/DM" publish≈'O "state =" O "type =" IN "> <Workshop DM: OriginalPointer>

<Atelier.DM:Pointer externaljd = "description for access to physical data" source_name = "" source_site = "" source_type = "" type = "" /> </ Workshop. DM: OήginalPointer>

<Workshop.DM:ObjectProxy type≈ "HOME">

<Workshop.DM:PointerexternalJd= "description for access to physical data" /> <Workshop. DM: FrameworkMetaData xmlns: Workshop.DM = "http://www.societe.com/egat/Atelier/DM"> <Workshop.DM:Attributes.Generic acl_name = "Prive" db_type = "HOME" exiernaljd = "description for access to the physical data "id =" identifying "mdbJnstance =" MDB_exploit "modification_date =" "name =" my blue house "source =" CMSDK "status =" Pήvate "/>

<Workshop.DM:Attributes.Specific state = "ruined" nbjenetre≈ "4" nb_pieces = "10"/><Workshop.DM:Links> FR2009 / 000569

35

<Workshop.DM:Link comments = "link deletion" date≈ "" id_F0_1 = "identifier Data 805" id_F0__2 = "IPT identifier 815" mdb_instanœ = "MDB_exploit" owner = "to39751" subtype = "subtype of link" type = "HISTORY" xmlns: Workshop.DM = "http://www.societe.com/egat/Atelier/DM" />

</Atelier.DM:Links> </ Workshop.DM:FrameworkMetaData> </ Workshop. DM: ObjectProxy>

</ Workshop. DM: EEObjectProxy>

Code snippet 7:

<Workshop. DM: EEObjectProxy xmlns: Workshop. DM = "http: // www.company.com/egat/Workshop/DM" publish = "1" state = "1" type = "OUT"> <Workshop. DM: SandboxPointer>

<Workshop.DM:Pointer extemal_id = "description for access to the sandbox" /> </Workshop.DM:SandboxPointer>

<Atelier.DM; FinalPointer>

<Workshop.DM:Pointer external_id = "description for access to physical data" /> </ Workshop. DM: FinalPointer> <Workshop.DM:ObjectProxytype= "HOME"> <Workshop.DM:Pointer external_id = "description for access to physical data" />

<Workshop. DM: FrameworkMetaData xmlns: Workshop.DM = "http://www.societe.com/ega1/Atelier/DM">

<Atelier.DM:Attributes. Generic acl_name = "Prive" db_type = "HOUSE" external_id = "description for access to physical data" id = "login" mdb_instance = "MDB_exploit" edit_date = ^: "" name = "my blue home" source = "CMSDK" status = "Private"/>

<Workshop.DM:Attributes.Specific state = "livable" nb_window = "6" nb_pieces = "12" /> <Workshop.DM:Links>

<Workshop.DM:Link comments = "description of the link" date = "" id_FO_1 = "IPT identifier 815" id_FO_2 = "identifier Data 810" mdbJnstance = "MDB_exploit" owner = "to39751" subtype = "subtype of link" type = "HI STORY" xmlns: Workshop.DM = "http://www.societe.com/egat/Atelier/DM" />

</ Workshop. DM: Links> </Atelier.DM:FrameworkMetaData> </Atelier.DM:ObjectProxy>

</ Workshop. DM: EEObjectProxy>

Code snippet 8:

<Workshop.DM:EEObjectProxy xmlns: Workshop.DM = "http://www.societe.com/egat/Atelier/DM" publish = "1" state = "1" type = "OUT"> <Workshop. DM: SandboxPointer>

<Workshop.DM:Pointer external_id = "description for sandbox access" source_name = "" source_site = "" sourcejype≈ "" type = "">

</ Workshop. DM: SandboxPointer> <Workshop.DM:FinalPointer>

<Atelier.DM:Pointer extemal_id = "description for access to physical data" /> </ Workshop. DM: FinalPointer> <Workshop.DM:ObjectProxy type = "HOME">

<Atelier.DM:Pointer external_id = "description for access to the physical data" /> <Atelier.DM:FrameworkMetaData xmlns: Atelier.DM = "http: // www. Societe.com/egat/Atelier/DM">

<Atelier.DM:Attributes. Generic acl_name = "Prive" db_type = "HOUSE" externaljd = "description for access to physical data" id = "login" mdb_instance = "MDB_exploit" modification_date = "" name = "my blue house" source = "CMSDK" status = "Private"/>

<Workshop.DM:Attributes.Specific state = "livable" nb_window = "6" nb_pieces = "12" /> <Workshop.DM:Links> <Workshop.DM:Link comments = "deschption of the link" date≈ "" id_F0_1 = "IPT identifier

815 "id_F0_2 =" identifier Data 810 "mdb_instanœ =" MDB_exploit "owner =" to39751 "subtype =" subtype of link "iype =" HISTORY "xmlns: Aielier.DM =" http://www.societe.com/egat / Workshop / DM "/>

<Workshop.DM:ϋnk comments = "link description" date≈ "" idJF0_1 = "identifier Data 810" id_F0_2≈ "IPT ID 830" mdb_instance = "MDB_exploit" owner = "to39751" subtype = "link type" type = "HISTORY" xmlns: Workshop.DM = "http://www.societe.com/egat/Atelier/DM" />

</ Workshop. DM: EEObjectProxy>

Code snippet 9:

<Ateiier.DM:EEObjectProxy xmlns: Workshop.DM = "http://www.societe.com/egat/Atelier/DM" publish = "1" state = "1" type = "θυτ ⁿ ><Workshop.SandboxPointer>

<Workshop.DM:Pointer externaljd = "description for sandbox access" /> </Workshop.DM:SandboxPointer> <Workshop. DM: FinalPointer> <Workshop.DM:Pointer external_id = "descπption for access to the physical data" />

</Atelier.DM:FinalPointer> <Workshop.DM:ObjectProxytype- 'HOME'>

<Atelier.DM:Pointerexternal_id= "description for access to the physical data" /> <Atelier.DM:FrameworkMetaData xmlns: Atelier.DM = "http://www.societe.com/egat/Atelier/DM">

<Atelier.DM:Attήbutes.Generic acl_name = "Prive" dbJype = "HOUSE" external_id = "description for access to physical data" id = "login" mdb_instance = ^: "MDB_exploit" modification_date = "" name = "my blue house "source =" CMSDK "staius =" Private "/><Workshop.DM:Attributes.Specificetai≈" lives "nb_window =" 6 "nb_pieces =" 12 "/>

<Atelier.DM:Links>

<Workshop.DM:Link comments = "link description" date = "" idJFO_1 ^ 'IPT ID 830 "id_FO_2 =" identifier Data 835 "mdb_instance =" MDB_exploit "owner =" to39751 "sufferedype =" subtype of link "type ≈ΗISTORY "xmlns: Workshop.DM =" http://www.societe.com/egat/Atelier/DM "/>

<Workshop.DM:Link comments = "link description" date = "" id_F0_1 = "IPT ID 830" id_FO_2 = "identifier Data 835" mdb_instance≈ "MDB_exploit" owner = "to39751" subtype = "link type" type ≈ΗISTORY "xmlns: Workshop.DM =" http://www.societe.com/egat/Atelier/DM "/> <Workshop.DM:Link comments =" link description "date =" "id_FO_1 =" IPT ID

830 "id_FO_2 =" identifier Data 835 "mdb_instance =" MDB_exploit "owner =" to39751 "subtype≈" under link type "type =" HISTORY "xmlns. Workshop.DM =" http: // www. company, com / egaϋ Αielier / DM "/>

</ Workshop. DM: Links> </ Workshop. DM: FrameworkMetaData>

</ Workshop. DM: ObjectProxy>

</Atelier.DM:EEObjectProxy>

Table 2.

ID1 5 8 3 5 ...

ID2 8 5 1 1 ... ... ... ...

Claims

0056938REVENDICATIONS

A data management method in a collaborative service-oriented workshop implemented in a computer system, the method being characterized in that said collaborative service oriented workshop is adapted to process objects associated with data representative of real data and objects. associated with process representative data and that the method comprises the following steps,

selecting (230) at least one first object comprising at least one link, called first link, to a second object, distinct from said first object;

- access (240, 245) to at least one link to a third object, called second link, said second link being included in one of said first and second objects, said third object being distinct from said first and second objects; and,

establishing (245, 255) a link between the data associated with said third object and the other of said first and second objects.

The method of claim 1 wherein the data associated with said first object is representative of a process.

3. The method of claim 2 wherein the data associated with said second object are at least partially obtained from said process or wherein said process is applied to at least a portion of said data associated with said second object.

The method of any one of the preceding claims further comprising a step of constructing (215) a data tree according to said first and second links.

5. Method according to any one of the preceding claims, characterized in that said steps of accessing at least one link and establishing a link are recursively repeated to establish a link between data associated with at least two links. separate objects.

6. Method according to any one of the preceding claims, wherein at least one of said links contained in one of said objects is stored in a link table.

The method of any one of the preceding claims wherein said process utilizes at least one function external to said collaborative service-oriented shop.

The method of any of the preceding claims wherein said objects are stored in a centralized database (125).

The method of any of the preceding claims wherein said data associated with said objects is stored in remote devices (130).

10. Computer program comprising instructions adapted to the implementation of each of the steps of the method according to any one of the preceding claims.