The following illustrative example shows a typical scenario of managing an ad-hoc study between two internal domain teams using different platforms (e.g. Architects using Dassault Systèmes’ 3D Experience platform and Simulation Specialists using MSC Software’s SimManager platform) and an external supplier (e.g. using Siemens’ TeamCenter platform) (see Figure 4). It is recognized that this does not cover the entire range of scenarios, and is only one of many use-cases which will be elaborated as part of the Application Activity Model. The use-case has the following steps: Initiate - Prepare - Perform - Review - Initiate | |
Initiate design investigation studyDuring the concept phase of a new product family, an OEM Architect looks at the physical characteristics and performance simulation results for the current product and notices that:
The OEM Architect decides launch a top level “weight reduction” study controlling two parallel studies, “materials technology” and “simulation improvement”, to investigate these ideas. This is illustrated in Figure 5. Note: only the “materials technology” study will be elaborated in this illustrative example. | |
PrepareUsing the architect’s software platform, the OEM Architect creates a “materials technology” study with the following:
The OEM Architect then sets up a review with the OEM Simulation Experts in “Team B” with the result that the following high level tasks are identified for the study.
| |
PerformThe OEM Architect changes the study status to “launched”, this sends a notification to the OEM Simulation Experts, and their specialist’s software platform pulls the details from the architect’s software platform using MoSSEC web services (see Figure 7 below). | |
The OEM Simulation Experts review the request and, in discussion with the Supplier, adapts to include several intermediate steps needed to achieve the expected results. Figure 8 shows the expected results (for the “weight” part of the study) with connections to the inputs, and elaborated with additional steps for; simplifying the structural model; creating a mesh; and modelling the uncertainty from the structural simulation. This adapt step could occur at any point and any number of times during the lifecycle of the study, for example, if an initial set of results have too low confidence an alternative simulation could be included in the study. | |
The OEM Simulation Experts start work generating the expected results. Where the inputs are provided as links, the specialist’s software platform downloads the technical data from the linked platform. When each result is available the specialist’s software platform updates the architect’s software platform with links to the results and an updated status, as shown in the adjacent image where change in status is indicated by green border. | |
When all the inputs are available that are needed for the step that has been delegated to the Supplier, a notification is sent to the Supplier. At the same time the associated inputs are posted to a collaboration hub (e.g. Eurostep’s Share-A-space) that is outside both the OEM’s and Supplier’s firewalls though controlled by the OEM. For this example the collaboration data is posted using MoSSEC web services, and the technical data is posted using file exchange e.g. in STEP AP242 Part28 format. Unlike the exchange between the OEM teams where links to the technical data were used, supplier does not have permission to follow the links through the firewall so the technical data must also be exchanged. Both the collaboration data and the technical data can include associated information rights and security classifications. | |
Exchange with supplier through firewalls via collaboration hub In a similar way, the supplier generates the expected results and post updates of the collaboration data (e.g. status updates and weight KPI values) and technical data (e.g. results files) and any other pertinent information (e.g. assumptions made during simulation – see Figure 11) back to the collaboration hub. These are retrieved by the Simulation Specialist platform and exchanged with the architect’s platform When all the results data and KPI have been computed, the simulation specialist assesses if the objectives have been met, and updates the verification status accordingly. At the conclusion of the perform phase the data is sent from the specialist’s platform to the architect’s platform with the result | |
ReviewAt any point in the lifecycle of the study the OEM Architect can review the progress and any available results. In this illustration it is assumed that all the results have been published and the OEM reviews the following (see Figure 12):
As the results from the other parts of the study become available the OEM architect discovers that although the weight is improved by using the new material technology, the manufacturing cost has significantly increased. By looking at the costs in more detail it becomes apparent that one part of the structure has more impact on these costs than the rest. | |
Initiate follow-up studyThe OEM Architect decides to launch a follow-up study where the part of the structure that had highest impact on the manufacturing cost uses conventional materials and the rest of the structure uses the new material. A review of the traceability from the different studies shows that the results from some of the intermediate steps can be reused (e.g. the simplified model and the mesh model) and other steps can use the same models to generate results from the updated inputs. Therefore a new study is launched that includes results from the previous studies and adds new tasks to rerun the results computation for the updated inputs. |