

Entities Lifecycle

We explain in this page the Lifecycle that entities go through on our platform from the moment of their design by the users, to the moment they are sent to the computing clusters of our infrastructure for Job Execution. This lifecycle concludes when the relevant entity Properties are extracted from the output of the Job simulation, and finally stored as structured data in the database.

The entity lifecycle is portrayed in the diagram below, where the four main logical steps involved are labelled. Each of these steps is reviewed separately in the ensuing explanations. Further information about the general data lifecycle within our platform can be retrieved here.

1. Job Design

New simulation Jobs can be designed by the user with the help of the Job Designer Interface. Jobs can be designed in this way by assembling together a material structure with a corresponding Workflow computation.

2. Submit and Execute Jobs

The Jobs designed in the preceding step can then be submitted to our computing clusters for their execution.

3. Extraction of Properties

At the end of Job execution, the computed Properties can finally be extracted and refined from the corresponding simulation output, for their final storage in the database as structured data.

4. Analysis of Results

The user is then free to inspect, manipulate and analyse the entity properties output by simulations by retrieving them from the relevant Account-owned entity collections, as displayed to the user under the corresponding Explorer Interface for the given entity type.