Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/46—Multiprogramming arrangements
  • G06F9/54—Interprogram communication
  • G06F9/544—Buffers; Shared memory; Pipes
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q10/00—Administration; Management
  • G06Q10/10—Office automation; Time management

Definitions

• the present invention relates to computer architectures for collaborative work and more particularly to a data management method for 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.
• 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.
• these specialists may be located, geographically, in separate locations.
• 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.
• 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.
• Python 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.
• 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,
• 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 to allow a global management thereof.
• the method further comprises a step of receiving at least one additional information, said additional information being stored in said object associated with said at least one datum for characterizing said at least one datum.
• said at least one characteristic information comprises at least one attribute common to a plurality of data.
• said at least one characteristic information comprises at least one attribute specific to said at least one datum.
• Said object further preferably comprises a link to a second object, separate from said object called the first object for linking objects together and, thus, to provide the means to follow a relationship gradually between several objects.
• the method further comprises a step of determining the consistency of said first object according to said link to said second object for characterizing an object according to predetermined rules.
• the method further comprises the following steps,
• the method according to the invention is thus able to execute processes represented by objects and to establish links between the objects associated with the processes executed and the objects associated with the real data implemented by the processes, that is, ie, for example, used or produced by processes.
• the method further comprises the following steps,
• the method according to the invention is thus able to execute processes represented by objects, to produce new real data, to create objects associated with these new real data and to to establish links between the objects associated with the processes executed and the created objects associated with the new real data.
• At least one of said objects is stored in the form of at least one table or at least one XML file.
• the invention also relates to a computer program comprising instructions adapted to the implementation of each of the steps of the method described above.
• 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.
• 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.
• 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.
• the architecture 100 is adapted to manipulate computer objects representing data in the broadest sense of the term, these data being representative of a real object, for example an aircraft, or a process such as a data processing process. aerodynamic drag calculation.
• 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.
• framework object proxies in English terminology or FO proxies
• Instantiated process models are instances of process models, that is, process models applied to one or more objects.
• the process models, called process templates in English terminology or PT are generic, it is for example a process of building a living room from several chairs and a table, a process renovation of a home or moving process.
• Instantiated process models are represented as objects and can be handled as such in the collaborative service-oriented workshop.
• Meta-data 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.
• 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.
• 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".
• 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.
• code snippet 2 illustrates the XML type description of a type of metadata used to describe a chair.
• the metadata advantageously comprise a generic part and a specific part.
• the generic part includes, in particular, the following elements,
• - a creation date; an identifier of the data which can be a key or a URL making it possible to access the data;
• 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 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.
• 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.
• 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.
• the metadata can be represented as tables.
• 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 links are not included in the table representing 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.
• the information stored in the metadata tables and in the link table makes it possible to manipulate all the data, current and future, collaborative service oriented workshop as well as build data models.
• 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.
• HMI human-machine interface
• the user interface can use, in particular, queries of the SQL type (acronym for Structured! Query Language in English terminology). Saxon). This manual recording of metadata proves interesting for the addition specific information that can not be extracted automatically from the data when importing the object into the shop floor.
• 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.
• 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
• the 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 different databases 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 when 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 movement of the data during execution.
• the execution engine 115 also preferably comprises an interface with applications using workflows in English terminology such as 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.
• FIG. 2a is a simplified block diagram of the data manager 110.
• Corba (acronym for Common Object Request Broker Architecture, Corba is a trademark)
• data are created in the various databases of data (not shown).
• a mechanism 200 for extraction, transformation and loading 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 previously described, they are stored with them 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 the traceability between the different data produced or used during the execution of processes.
• links There are several types of links, including the following: - user links manually determined by the user between two data;
• - 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;
• This type of link is created automatically when phase of publishing data during or at the end of the execution of an instantiated process (IPT).
• IPT instantiated process
• the data contains all the histories, in particular as regards the executions of processes, the versions, the configurations, the users and the models.
• the data models that is the data trees
• data models are specific to the data handled in the collaborative service-oriented workshop.
• 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.
• 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, that is to say a view presenting the relations between objects, which can to be transmitted to a user in the form of data model views 215.
• the user can view objects and relationships as object views 220 and relationship views 230, such as lists.
• 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.
• a link to a second object, contained in this first object is accessed (step 235).
• 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.
• 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.
• 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.
• the parameters, the code and the data information necessary for the execution of the process are extracted from the XML document.
• 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 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.
• 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.
• 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 process. input data;
• 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.
• the executable code is executed by the collaborative service-oriented workshop or by an external application.
• 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.
• MC ModelCenter
• FIG. 5 illustrates an example of encapsulation of a ModelCenter model in a process model.
• 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.
• 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 process thus formatted 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).
• 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.
• 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.
• encapsulation One of the purposes of encapsulation is to adapt the process models according to a predetermined format.
• 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.
• 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,
• Figure 5 illustrates an exemplary encapsulation of a ModelCenter 500 model in a process model 505. 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.
• 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.
• 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.
• the degree of traceability of the data is thus determined by the functions performed by the collaborative service-oriented workshop and by external applications.
• 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.
• 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.
• process models composites that refer to several unit process models or themselves composites.
• 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;
• ModelCenter execution identifier if the instantiated process model refers to a ModelCenter type function
• 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 as well as 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 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.
• PT Process Template
• DM Data Management
• ModelCenter that is, a particular process manager.
• 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 sections related to the inputs, outputs and parameters themselves include arguments 645.
• the process model implicitly includes information about specific models 650-1 to 650-n such as EDMG models
• ModelCenter receives information from a particular model 655.
• the data specified in sections 610, 615 and 620 are derived from objects 660 which themselves include links (665 and 670) to other objects.
• 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.
• 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).
• 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.
• the conditions on the inputs and the inputs / outputs are checked (step 740).
• 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.
• 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.
• step 745 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 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.
• 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.
• 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.
• 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.
• the execution engine 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.
• 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.
• 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.
• 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.
• 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 meta-data are of the IN type, that is, they do not correspond to data created by an instantiated process model.
• 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". ".
• 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.
• 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".
• a link has been created between the objects associated with the data 805 and the instantiated process model 815.
• 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.
• 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".
• a link has been created between the object associated with the data 810 and the object associated with the instantiated process model 815.
• the object associated with the instantiated process model 815 it is possible to establish the link between the data 805 and 810.
• 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.
• 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.
• 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 can then be expressed in the form given in the appendix under the reference "code extract 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.
• 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.
• 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:
• CPU Central Processing Unit
• a read-only memory 904 (ROM, acronym for Read OnYy Memory in English terminology) that may include the programs “Prog”, “Prog1” and “Prog2";
• RAM Random Access Memory
• communication interface 918 adapted to transmit and receive data.
• 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 include "Prog" programs,
• a memory card reader 914 adapted to receive a memory card 916 and to read or write to it data processed 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 through 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.
• the memory card 916 can 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.
• 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.
• 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.
• 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.

Landscapes

• Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• Business, Economics & Management (AREA)
• Physics & Mathematics (AREA)
• Software Systems (AREA)
• Entrepreneurship & Innovation (AREA)
• Human Resources & Organizations (AREA)
• Strategic Management (AREA)
• General Physics & Mathematics (AREA)
• Operations Research (AREA)
• Tourism & Hospitality (AREA)
• Quality & Reliability (AREA)
• General Business, Economics & Management (AREA)
• Marketing (AREA)
• Economics (AREA)
• Data Mining & Analysis (AREA)
• General Engineering & Computer Science (AREA)
• Stored Programmes (AREA)
• Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Applications Claiming Priority (2)

Publications (1)

Family

ID=40185044

Family Applications (1)

Country Status (5)

Families Citing this family (8)

Citations (1)

Family Cites Families (7)

• 2008
  • 2008-05-14 FR FR0853121A patent/FR2931274B1/fr not_active Expired - Fee Related
• 2009
  • 2009-05-14 EP EP09757686A patent/EP2297681A1/de not_active Withdrawn
  • 2009-05-14 WO PCT/FR2009/000566 patent/WO2009147310A1/fr active Application Filing
  • 2009-05-14 US US12/991,527 patent/US8706702B2/en not_active Expired - Fee Related
  • 2009-05-14 JP JP2011508973A patent/JP5524186B2/ja not_active Expired - Fee Related

Patent Citations (1)

Non-Patent Citations (3)

Also Published As

Similar Documents

Legal Events