Package: TopLevelSequence

Activity: TopLevelSequence

(from Package:TopLevelSequence)

This is the Top Level Sequence, the highest level overview of what is occuring during each stage of a "Weight Reduction Study".

Figure:act_WPEx_TopLevelSequence

Block Block Block Block Block

This Activity has no parameters

Call Behaviour: ConsiderCurrentProductFamily

Local name:ConsiderCurrentProductFamily

During the concept phase of a new product family, an OEM Architect looks at the physical characterstics and performance simulation results for the current product.

This has no arguments

Call Behaviour: InitiateStudy

Local name:InitiateStudy

The OEM Architect decides they wish to initiate a top level "weight reduction" study controlling two parallel studies, "materials technology" and "simulation improvement".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
originalArchitecture

The original architecture used in the original product study.

Output1BDAArchitectureMB_ArchitectureBaseline
newArchitecture

The new architecture to be used in the new study.

Output1BDAArchitectureMB_Architecture_2
Study

The "MaterialsTechnologyStudy" is taken from the activity Initiate Study to be prepared in Prepare Study.

Output1BDAStudyMaterialsTechnologyStudy

Call Behaviour: PrepareStudy

Local name:PrepareStudy

The OEM Architect prepares the "materials technology" study for launch.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
Architecture

The new architecture of the new study is input to be used in preparing the new study for execution.

Input1BDAArchitectureMB_Architecture_2
Study

The "MaterialsTechnologyStudy" is taken from the activity Initiate Study to be prepared in Prepare Study.

Input1BDAStudyMaterialsTechnologyStudy
updatedStudy

The "MaterialsTechnologyStudy" is taken from the activity Prepare Study to be executed in Perform Study.

Output1BDAStudyMaterialsTechnologyStudy
AMN

The new Associative Model Network associated with "MaterialsTechnologyStudy" is output to be used in "PerformStudy".

Output1BDAAssociativeModelNetworkMaterialsTechnologyStudy_AMN

Call Behaviour: PerformStudy

Local name:PerformStudy

The study is launched and undertaken by the OEM teams and external suppliers.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
Study

The "MaterialsTechnologyStudy" is taken from the activity Prepare Study to be executed in Perform Study.

Input1BDAStudyMaterialsTechnologyStudy
AMN

The new Associative Model Network associated with "MaterialsTechnologyStudy" is input to execute the study.

Input1BDAAssociativeModelNetworkMaterialsTechnologyStudy_AMN
Assumption

Any reasonable assumptions made by the Supplier are output from the activity Perform Study to be reviewed in Review Study.

Output1BDAAssumptionTemperatureAssumption

Call Behaviour: ReviewStudy

Local name:ReviewStudy

The OEM Architect reviews the progress of any available results.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
Architecture

The Baseline Architecture output from Prepare Study is input into Review Study to be used as as supporting justification for the Suppliers assumptions to be approved by the OEM Simulation Expert.

Input1BDAArchitectureMB_Architecture_2
Assumption

Any assumptions made by the Supplier in Perform Study are input into Review Study to be reviewed.

Input1BDAAssumptionTemperatureAssumption

Package: ConsiderCurrentProductFamily

Activity: ConsiderCurrentProductFamily

(from Package:ConsiderCurrentProductFamily)

During the concept phase of a new product family, the OEM Architect looks at the physical characterstics and performance simulation results for the current product.

Figure:act_WPEx_ConsiderCurrentProductFamily

Block Block Block Block Block Block Block Block Block

Figure:bdd_WPEx_CurrentProductStudy

Figure:bdd_WPEx_OtherProductStudy

This Activity has no parameters

Call Behaviour: Select (from ../Behaviours/ArchitectureCockpit::LocalGenericBehaviours)

Local name:Select

The OEM Architect views the relations to this breakdown element, until they find analysis results to compare from a previously conducted study.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
selectedItem

The Current Product architecture, "MB_ArchitectureBaseline" is selected.

Output1..*No type definedMB_ArchitectureBaseline
Call Behaviour: NavigateArchitecture (from ../Behaviours/ArchitectureCockpit/DefineManageVirtualArchitecture::ManageArchitectures)

Local name:NavigateArchitecture

The OEM Architect navigates the Current Products architecture.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
architecture

The Current Product architecture, "MB_ArchitectureBaseline" is input to be navigated.

Input1BDAArchitectureMB_ArchitectureBaseline
Call Behaviour: Select (from ../Behaviours/ArchitectureCockpit::LocalGenericBehaviours)

Local name:Select

The OEM Architect selects the breakdown element of interest.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
selectedItem

The breakdown element, "MB_CrankGears" is selected by navigating the architecture, "MB_ArchitectureBaseline".

Output1..*No type definedMB_CrankGears
Call Behaviour: SearchInteractive (from ../Behaviours/ArchitectureCockpit::LocalGenericBehaviours)

Local name:SearchInteractive

The OEM Architect searches for similar breakdown elements within the organization.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
searchCriteria

The breakdown element "MB_CrankGears" is used as the search criteria to find similar breakdown elements within the organization.

Input0..*No type definedMB_CrankGears
searchResults

The search within the OEM Organization, resulted in the breakdown element "RB_CrankGears" being returned.

Output0..*No type definedRB_CrankGears
Call Behaviour: DisplayNavigationView (from ../Behaviours/ArchitectureCockpit::Visualization)

Local name:DisplayNavigationView

The OEM Architect displays the relations to this breakdown element, until they find analysis results to compare, from a previously conducted study.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
objectsToDisplay

The relationships to the breakdown element, "RB_CrankGears", are displayed for the OEM Architect to navigate.

Input1..*BDAIdentifiableObjectRB_CrankGears
Call Behaviour: DisplayNavigationView (from ../Behaviours/ArchitectureCockpit::Visualization)

Local name:DisplayNavigationView

The OEM Architect displays the relations to this breakdown element, until they find analysis results to compare, from a previously conducted study.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
objectsToDisplay

The relationships to the breakdown element, "MB_CrankGears", are displayed for the OEM Architect to navigate.

Input1..*BDAIdentifiableObjectMB_CrankGears
Call Behaviour: Select (from ../Behaviours/ArchitectureCockpit::LocalGenericBehaviours)

Local name:Select

The OEM Architect select the analysis results associated with the breakdown element to compare, from a previously conducted study.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
selectedItem

The Other Products "CrankGearAnalysisResults" are selected by navigating from "RB_CrankGears" to compare with those results from the Current Product.

Output1..*No type definedRB_CrankGearAnalysisResults
Call Behaviour: Select (from ../Behaviours/ArchitectureCockpit::LocalGenericBehaviours)

Local name:Select

The OEM Architect select the analysis results associated with the breakdown element to compare, from a previously conducted study.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
selectedItem

The Current Products "CrankGearAnalysisResults" are selected by navigating from "MB_CrankGears" to compare with those results from the Other Product.

Output1..*No type definedMB_CrankGearAnalysisResults
Call Behaviour: GraphicalComparison (from ../Behaviours/ArchitectureCockpit/EvaluateConceptsDecide::Compare)

Local name:GraphicalComparison

The OEM Architect compares the Analysis Results from the two studies and acknowledges the possible benefits from conducting a new materials study on the current product.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
resultsToCompare

The two "CrankGearAnalysisResults" from the Current Product and Other Product are input to be compared graphically.

Input1..*BDAIdentifiableObjectRB_CrankGearAnalysisResults;
MB_CrankGearAnalysisResults

Package: InitiateStudy

Activity: InitiateStudy

(from Package:InitiateStudy)

Figure:act_WPEx_InitiateStudy

Block Block Block Block Block Block

Table: InitiateStudy Parameters

Name Notes Direction Multiplicity Type
Study

The prepared study is output from the activity to then be undertaken in "PerformStudy".

out1BDAStudy
originalArchitecture

The Baseline Architecture of the Mountain Bike is output here to be used as supporting justification for any assumptions made during the review stage of the study, "ReviewStudy".

out1BDAArchitecture
newArchitecture

The new architecture to be used in the new study.

out1BDAArchitecture
Call Behaviour: InitiateDesignInvestigationStudy

Local name:InitiateDesignInvestigationStudy

The OEM Architect initiates the Design Investigation Study "WeightReductionStudy" which contains both a "MaterialsTechnologyStudy" and a "SimulationImprovementStudy".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
Studies

These are the studies which are created and initiated in the activity "InitiateDesignInvestigationStudy".

Output1..*BDAStudyWeightReductionStudy;
SimulationImprovementStudy;
MaterialsTechnologyStudy
Call Behaviour: Select (from ../Behaviours/ArchitectureCockpit::LocalGenericBehaviours)

Local name:Select

"MB_ArchitectureBaseline" is selected by the OEM Architect as the initial architecture for the study.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
selectedItem

"MB_ArchitectureBaseline" is output, having been selected by the OEM Architect.

Output1..*No type definedMB_ArchitectureBaseline
Call Behaviour: AddStudyInputData (from ../Behaviours/ArchitectureCockpit/SetupOrchestrate_trade_off_studies::DefineStudy)

Local name:AddStudyInputData

The architecture of the original study, "MB_ArchitectureBaseline" is added to the study, "MaterialsTechnologyStudy".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
study

The study, "MaterialsTechnologyStudy" is input.

Input1BDAStudyMaterialsTechnologyStudy
inputsToAdd

The original architecture, "MB_ArchitectureBaseline" is input to be added to the study.

Input1No type definedMB_ArchitectureBaseline
updatedStudy

"MaterialsTechnologyStudy" is output after it has had "MB_ArchitectureBaseline" added.

Output1BDAStudyMaterialsTechnologyStudy
approvals

No output required.

Output0..*BDAApprovalNo connection found
assumptions

No output required.

Output0..*BDAAssumptionNo connection found
justifications

No output required.

Output0..*BDAJustificationNo connection found
Call Behaviour: AddStudyInputData (from ../Behaviours/ArchitectureCockpit/SetupOrchestrate_trade_off_studies::DefineStudy)

Local name:AddStudyInputData

The architecture of the original study, "MB_ArchitectureBaseline" is added to the study, "SimulationImprovementStudy".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
study

The study, "SimulationImprovementStudy" is input.

Input1BDAStudySimulationImprovementStudy
inputsToAdd

The original architecture, "MB_ArchitectureBaseline" is input to be added to the study.

Input1No type definedMB_ArchitectureBaseline
updatedStudy

"SimulationImprovementStudy" is output after it has had "MB_ArchitectureBaseline" added.

Output1BDAStudySimulationImprovementStudy
approvals

No output required.

Output0..*BDAApprovalNo connection found
assumptions

No output required.

Output0..*BDAAssumptionNo connection found
justifications

No output required.

Output0..*BDAJustificationNo connection found
Call Behaviour: AddStudyInputData (from ../Behaviours/ArchitectureCockpit/SetupOrchestrate_trade_off_studies::DefineStudy)

Local name:AddStudyInputData

The architecture of the original study, "MB_ArchitectureBaseline" is added to the study, "WeightReductionStudy".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
study

The study, "WeightReductionStudy" is input.

Input1BDAStudyWeightReductionStudy
inputsToAdd

The original architecture, "MB_ArchitectureBaseline" is input to be added to the study.

Input1No type definedMB_ArchitectureBaseline
updatedStudy

"WeightReductionStudy" is output after it has had "MB_ArchitectureBaseline" added.

Output1BDAStudyWeightReductionStudy
approvals

No output required.

Output0..*BDAApprovalNo connection found
assumptions

No output required.

Output0..*BDAAssumptionNo connection found
justifications

No output required.

Output0..*BDAJustificationNo connection found
Call Behaviour: CreateArchitectureAlternative (from ../Behaviours/ArchitectureCockpit/DefineManageVirtualArchitecture::DefineArchitectures)

Local name:CreateArchitectureAlternative

An alternative architecture, "MB_Architecture_2", based on "MB_ArchitectureBaseline" from the original product study is created for the new study, "MaterialsTechnologyStudy".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
architectureForAlternative

The original architecture, "MB_ArchitectureBaseline" is input to have an alternative of itself created for "MaterialsTechnologyStudy".

Input1BDAArchitectureMB_ArchitectureBaseline
context

"MaterialsTechnologyStudy" is input as the context, requiring an alternative architecture.

Input0..1No type definedMaterialsTechnologyStudy
alternativeArchitecture

The new alternative architecture, "MB_Architecture_2" based on "MB_ArchitectureBaseline" is output.

Output1BDAArchitectureMB_Architecture_2

Package: InitiateDesignInvestigationStudy

Activity: InitiateDesignInvestigationStudy

(from Package:InitiateDesignInvestigationStudy)

The OEM Architect initiates the Design Investigation Study "WeightReductionStudy" which contains both a "MaterialsTechnologyStudy" and a "SimulationImprovementStudy".

Figure:act_WPEx_InitiateDesignInvestigationStudy

Block Block Block Block Block Block Block

Figure:bdd_WPEx_WeightReductionStudy_1

Table: InitiateDesignInvestigationStudy Parameters

Name Notes Direction Multiplicity Type
Studies

These are the studies which are created and initiated in the activity "InitiateDesignInvestigationStudy".

out1..*BDAStudy
Call Behaviour: CreateNewStudyContainer (from ../Behaviours/ArchitectureCockpit/SetupOrchestrate_trade_off_studies::DefineStudy)

Local name:CreateNewWeightReductionStudyContainer

Called to create the container for the "WeightReductionStudy".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
study

The new study container is created as "WeightReductionStudy".

Output1BDAStudyWeightReductionStudy
Call Behaviour: CreateNewStudyContainer (from ../Behaviours/ArchitectureCockpit/SetupOrchestrate_trade_off_studies::DefineStudy)

Local name:CreateNewMaterialsTechStudyContainer

Called to create the container for the "MaterialsTechnologyStudy".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
study

The new study container is created as "MaterialsTechnologyStudy".

Output1BDAStudyMaterialsTechnologyStudy
Call Behaviour: CreateNewStudyContainer (from ../Behaviours/ArchitectureCockpit/SetupOrchestrate_trade_off_studies::DefineStudy)

Local name:CreateNewSimulationImprovementStudyContainer

Called to create the container for "SimulationImprovementStudy".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
study

The new study container is created as "SimulationImprovementStudy".

Output1BDAStudySimulationImprovementStudy
Call Behaviour: AddStudyWBSContext (from ../Behaviours/ArchitectureCockpit/SetupOrchestrate_trade_off_studies::DefineStudy)

Local name:AddMaterialsTechStudyWBSContext

Called to state that "WeightReductionStudy" is the parent of "MaterialsTechnologyStudy".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
study

"MaterialsTechnologyStudy" is input to be put into context.

Input1BDAStudyMaterialsTechnologyStudy
parentStudy

"WeightReductionStudy" is input to have its relationship to "MaterialsTechnologyStudy" assigned.

Input1BDAStudyWeightReductionStudy
updatedParentStudy

The updated "WeightReductionStudy" is output with the relationship "WeightReductionStudy.manages MaterialsTechnologyStudy" now added.

Output1BDAStudyWeightReductionStudy
Call Behaviour: AddStudyWBSContext (from ../Behaviours/ArchitectureCockpit/SetupOrchestrate_trade_off_studies::DefineStudy)

Local name:AddSimulationImprovementStudyWBSContext

Called to state that "WeightReductionStudy" is the parent of "SimulationImprovementStudy".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
parentStudy

"WeightReductionStudy" is input to have its relationship to "SimulationImprovmentStudy" assigned.

Input1BDAStudyWeightReductionStudy
study

"SimulationImprovementStudy" is input to be put into context.

Input1BDAStudySimulationImprovementStudy
updatedParentStudy

The updated "WeightReductionStudy" is output with the relationship "WeightReductionStudy.manages SimulationImprovementStudy" now added.

Output1BDAStudyWeightReductionStudy
Call Behaviour: Select (from ../Behaviours/ArchitectureCockpit::LocalGenericBehaviours)

Local name:SelectJustification

Called to select the supporting justification "RB_CrankGearAnalysisResults" for the study "MaterialsTechnologyStudy".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
selectedItem

"RB_CrankGearAnalysisResults" is selected.

Output1..*No type definedRB_CrankGearAnalysisResults
Call Behaviour: AddJustificationToObjectWithSupport (from ../Behaviours/ArchitectureCockpit/EvaluateConceptsDecide::Decide)

Local name:AddMaterialsTechJustificationToObjectWithSupport

Called to record the justification "RB_CrankGearAnalysisResults" for performing "MaterialsTechnologyStudy".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
itemToBeJustified

"MaterialsTechnologyStudy" is input to be justified.

Input0..*BDAJustifiedItemMaterialsTechnologyStudy
itemSupportingJustification

"RB_CrankGearAnalysisResults" is input to support the justification for "MaterialsTechnologyStudy".

Input0..*BDAJustificationSupportItemRB_CrankGearAnalysisResults
text

No input required.

Input0..1No type definedNo connection found
relatedJustifications

No input required.

Input0..*BDAJustificationNo connection found
justification

"JustificationForStudy" is output as the justification for "MaterialsTechnologyStudy".

Output1..*BDAJustificationJustificationForStudy
justificationApprovals

No output required.

Output0..*BDAApprovalNo connection found

Package: PrepareStudy

Activity: PrepareStudy

(from Package:PrepareStudy)

The OEM Architect prepares the "materials technology" study for launch.

Figure:act_WPEx_PrepareStudy

Block Block Block Block Block Block Block

Table: PrepareStudy Parameters

Name Notes Direction Multiplicity Type
Study

The "MaterialsTechnologyStudy" is taken from the activity Initiate Study to be prepared in Prepare Study.

in1BDAStudy
Architecture

The new architecture of the new study is input to be used in preparing the new study for execution.

in1BDAArchitecture
updatedStudy

The "MaterialsTechnologyStudy" is taken from the activity Prepare Study to be executed in Perform Study.

out1BDAStudy
AMN

The new Associative Model Network associated with "MaterialsTechnologyStudy" is output to be used in "PerformStudy".

out1BDAAssociativeModelNetwork
Call Behaviour: DefineStudyParameters

Local name:DefineStudyParameters

The study parameters for the "MaterialsTechnologyStudy" are defined here.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
Study

The "MaterialsTechnologyStudy" is input here.

Input1BDAStudyMaterialsTechnologyStudy
updatedStudy

The updated "MaterialsTechnologyStudy" is output here.

Output1BDAStudyMaterialsTechnologyStudy
Inputs

The data that is input into the study is passed through here.

Output1..*No type definedMB_CrankGearAnalysisResults
MB_Geom_model
Requirements

The Study's requirements are output here.

Output1..*No type definedWeight10ReductionReqt;
WeightConfidenceReqt;
GeomConstraint
Call Behaviour: Select (from ../Behaviours/ArchitectureCockpit::LocalGenericBehaviours)

Local name:Select

The Architect selects themselves to be assigned to the collaborative review.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
selectedItem

Data relating to the Architect is passed into the datastore.

Output1..*No type definedArchitect
Call Behaviour: Select (from ../Behaviours/ArchitectureCockpit::LocalGenericBehaviours)

Local name:Select

The Architect selects the Simulation Expert to be assigned to the collaborative review.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
selectedItem

Data relating to the Simulation Expert is passed into the datastore.

Output1..*No type definedSimulationExpert
Call Behaviour: CreatePlannedCollaborativeReview (from ../Behaviours/ArchitectureCockpit::CollaborativeReview)

Local name:CreatePlannedCollaborativeReview

"The OEM Architect sets up a review with the OEM Simulation Experts in "Team B"..."

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
subject

No input required.

Input0..*BDAActivityItemNo connection found
collaborators

The collaborators "Architect" and "SimulationExpert" are input.

Input1..*BDAActorArchitect
SimulationExpert
plannedCollaborativeReviewContainer

The planned Collaborative Review is output as "plannedCollaborativeReview".

Output1No type definedplannedCollaborativeReview
Call Behaviour: DefineAssociativeModelNetwork

Local name:DefineAssociativeModelNetwork

MaterialsTechnologyStudy" is input to the activity to have its Associative Model Network created and assigned.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
Study

"MaterialsTechnologyStudy" is input to the activity to have its Associative Model Network created and assigned.

Input1BDAStudyMaterialsTechnologyStudy
updatedStudy

"MaterialsTechnologyStudy" is output having had its Associative Model Network, "MaterialsTechnologyStudy_AMN" assigned.

Output1BDAStudyMaterialsTechnologyStudy
VerificationEvidence

Model Instances and Key Value Instances are output as "VerificationEvidence" that will be used in the review stage of the study to determine the outcome of the study.

Output1..*No type definedMB_CrankGearStructuralModel_2;
MB_CrankGearAnalysisResults_2;
MB_CrankGear_WConfidence_2;
MB_CrankGearWeight_2;
MaterialsTechnologyStudy_AMN
AMN

The Associative Model Network, "MaterialsTechnologyStudy_AMN" is output.

Output1BDAAssociativeModelNetworkMaterialsTechnologyStudy_AMN
Call Behaviour: AddModelsToAssociativeModelNetwork

Local name:AddModelsToAssociativeModelNetwork

How objects are related is defined within this activity.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
Architecture

The Architecture, "MB_Architecture_2" is input as the architecture for "MaterialsTechnologyStudy".

Input1BDAArchitectureMB_Architecture_2
breakdownElement

The breakdown element of interest to the study for improvement is output as "MB_CrankGears".

Output1BDABreakdownElementMB_CrankGears
AnalysisResults

The Analysis Results of this study are stored in "MB_CrankGearAnalysisResults_2", here the container for these results is output ready to be populated.

Output1BDAModelInstanceMB_CrankGearAnalysisResults_2
Call Behaviour: DefineStudyVerificationObjectives

Local name:DefineStudyVerificationObjectives

The Verification Objectives which will be checked against later are assigned to the study here.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
Study

The study, "MaterialsTechnologyStudy" is input here to have its verification objectives defined and assigned.

Input1BDAStudyMaterialsTechnologyStudy
breakdownElement

The breakdown element of the product, "MB_CrankGears" are input here to be used as a point of reference to be improved in the objectives.

Input1No type definedMB_CrankGears
VerificationEvidence

Model Instances and Key Value Instances are input as "VerificationEvidence" that will be used in the review stage of the study to determine the outcome of the study.

Input1..*No type definedMB_CrankGearStructuralModel_2;
MB_CrankGearAnalysisResults_2;
MB_CrankGear_WConfidence_2;
MB_CrankGearWeight_2;
MaterialsTechnologyStudy_AMN
Requirements

The requirements of the study are input to the activity to be assigned to the study.

Input1..*No type definedWeight10ReductionReqt;
WeightConfidenceReqt;
GeomConstraint
Architecture

The architecture of the study is input to have the "satisfiedBy" conditions of the input requirements assigned.

Input1BDAArchitectureMB_Architecture_2
updatedStudy

The "MaterialsTechnologyStudy" is output from the activity having now been assigned its verification objectives.

Output1BDAStudyMaterialsTechnologyStudy

Package: DefineStudyParameters

Activity: DefineStudyParameters

(from Package:DefineStudyParameters)

The study parameters for the "MaterialsTechnologyStudy" are defined here.

Figure:act_WPEx_DefineStudyParameters

Block Block Block Block Block Block Block Block

Figure:bdd_WPEx_WeightReductionStudy_2

Table: DefineStudyParameters Parameters

Name Notes Direction Multiplicity Type
Study

The "MaterialsTechnologyStudy" is input here.

in1BDAStudy
updatedStudy

The updated "MaterialsTechnologyStudy" is output here.

out1BDAStudy
Requirements

The Study's requirements are output here.

out1..*No type defined
Inputs

The data that is input into the study is passed through here.

out1..*No type defined
Call Behaviour: Select (from ../Behaviours/ArchitectureCockpit::LocalGenericBehaviours)

Local name:SelectCompositeMaterial

The composite material of interest is selected.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
selectedItem

Data relating to the Composite Material of interest is output.

Output1..*No type definedCompositeMaterial
Call Behaviour: AddStudyVerificationObjectives (from ../Behaviours/ArchitectureCockpit/SetupOrchestrate_trade_off_studies::DefineStudy)

Local name:AddStudyVerificationObjectives

The study, "MaterialsTechnologyStudy" is updated and a requirement created.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
study

"MaterialsTechnologyStudy" is input to have the requirement "Weight10ReductionReqt" added.

Input1BDAStudyMaterialsTechnologyStudy
objectsToSatisfy

No input required.

Input0..*BDASatisfiedByObjectNo connection found
objectsAsEvidence

No input required.

Input0..*BDAVerificationEvidenceObjectNo connection found
requirement

No input required.

Input0..*BDARequirementObjectNo connection found
updatedStudy

"MaterialsTechnologyStudy" is output after having a requirement added.

Output1BDAStudyMaterialsTechnologyStudy
newRequirement

The requirement "Weight10ReductionReqt" is created and output.

Output0..*BDARequirementWeight10ReductionReqt
satisfiedBy

No output required.

Output0..*BDARequirementShouldBeSatisfiedNo connection found
verification

No output required.

Output0..*BDAVerificationNo connection found
otherObjectsCreatedOrUpdated

No output required.

Output0..*BDAIdentifiableObjectNo connection found
Call Behaviour: AddStudyVerificationObjectives (from ../Behaviours/ArchitectureCockpit/SetupOrchestrate_trade_off_studies::DefineStudy)

Local name:AddStudyVerificationObjectives

The study, "MaterialsTechnologyStudy" is updated and a requirement created.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
study

"MaterialsTechnologyStudy" is input to have the requirement "WeightConfidenceReqt" added.

Input1BDAStudyMaterialsTechnologyStudy
objectsToSatisfy

No input required.

Input0..*BDASatisfiedByObjectNo connection found
objectsAsEvidence

No input required.

Input0..*BDAVerificationEvidenceObjectNo connection found
requirement

No input required.

Input0..*BDARequirementObjectNo connection found
updatedStudy

"MaterialsTechnologyStudy" is output after having a requirement added.

Output1BDAStudyMaterialsTechnologyStudy
newRequirement

The requirement "WeightConfidenceReqt" is created and output.

Output0..*BDARequirementWeightConfidenceReqt
satisfiedBy

No output required.

Output0..*BDARequirementShouldBeSatisfiedNo connection found
verification

No output required.

Output0..*BDAVerificationNo connection found
otherObjectsCreatedOrUpdated

No output required.

Output0..*BDAIdentifiableObjectNo connection found
Call Behaviour: AddStudyVerificationObjectives (from ../Behaviours/ArchitectureCockpit/SetupOrchestrate_trade_off_studies::DefineStudy)

Local name:AddStudyVerificationObjectives

The study, "MaterialsTechnologyStudy" is updated and a requirement created.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
study

"MaterialsTechnologyStudy" is input to have the requirement "GeomConstraint" added.

Input1BDAStudyMaterialsTechnologyStudy
objectsToSatisfy

No input required.

Input0..*BDASatisfiedByObjectNo connection found
objectsAsEvidence

No input required.

Input0..*BDAVerificationEvidenceObjectNo connection found
requirement

No input required.

Input0..*BDARequirementObjectNo connection found
updatedStudy

"MaterialsTechnologyStudy" is output after having a requirement added.

Output1BDAStudyMaterialsTechnologyStudy
newRequirement

The requirement "GeomConstraint" is created and output.

Output0..*BDARequirementGeomConstraint
satisfiedBy

No output required.

Output0..*BDARequirementShouldBeSatisfiedNo connection found
verification

No output required.

Output0..*BDAVerificationNo connection found
otherObjectsCreatedOrUpdated

No output required.

Output0..*BDAIdentifiableObjectNo connection found
Call Behaviour: Select (from ../Behaviours/ArchitectureCockpit::LocalGenericBehaviours)

Local name:SelectCrankGearAnalysisResults

The Architect selects "MB_CrankGearAnalysisResults" as an input for the study.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
selectedItem

"MB_CrankGearAnalysisResult" is selected.

Output1..*No type definedMB_CrankGearAnalysisResults
Call Behaviour: Select (from ../Behaviours/ArchitectureCockpit::LocalGenericBehaviours)

Local name:SelectGeomModel

The Architect selects "MB_Geom_model" as an input for the study.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
selectedItem

"MB_Geom_model" is selected.

Output1..*No type definedMB_Geom_model
Call Behaviour: AddStudyInputData (from ../Behaviours/ArchitectureCockpit/SetupOrchestrate_trade_off_studies::DefineStudy)

Local name:AddStudyInputData

The previously selected inputs are added to the study, "MaterialsTechnologyStudy".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
study

"MaterialsTechnologyStudy" is passed into the activity here to have an input to the study assigned to it.

Input1BDAStudyMaterialsTechnologyStudy
inputsToAdd

"MB_CrankGearAnalysisResults" is passed in here to be assigned as an input to "MaterialsTechnologyStudy".

Input1No type definedMB_CrankGearAnalysisResults
updatedStudy

The updated version of 'MaterialsTechnologyStudy' containing the added input is passed out here.

Output1BDAStudyMaterialsTechnologyStudy
approvals

No output required.

Output0..*BDAApprovalNo connection found
assumptions

No output required.

Output0..*BDAAssumptionNo connection found
justifications

No output required.

Output0..*BDAJustificationNo connection found
Call Behaviour: AddStudyInputData (from ../Behaviours/ArchitectureCockpit/SetupOrchestrate_trade_off_studies::DefineStudy)

Local name:AddStudyInputData

The previously selected inputs are added to the study, "MaterialsTechnologyStudy".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
study

"MaterialsTechnologyStudy" is passed into the activity here to have an input to the study assigned to it.

Input1BDAStudyMaterialsTechnologyStudy
inputsToAdd

"MB_Geom_model" is passed in here to be assigned as an input to "MaterialsTechnologyStudy".

Input1No type definedMB_Geom_model
updatedStudy

The updated version of 'MaterialsTechnologyStudy' containing the added input is passed out here.

Output1BDAStudyMaterialsTechnologyStudy
approvals

No output required.

Output0..*BDAApprovalNo connection found
assumptions

No output required.

Output0..*BDAAssumptionNo connection found
justifications

No output required.

Output0..*BDAJustificationNo connection found

Package: DefineAssociativeModelNetwork

Activity: DefineAssociativeModelNetwork

(from Package:DefineAssociativeModelNetwork)

MaterialsTechnologyStudy" is input to the activity to have its Associative Model Network created and assigned.

Figure:act_WPEx_DefineAssociativeModelNetwork

Block

Figure:bdd_WPEx_MaterialsTechnologyStudy_AMN_Models

Table: DefineAssociativeModelNetwork Parameters

Name Notes Direction Multiplicity Type
Study

"MaterialsTechnologyStudy" is input to the activity to have its Associative Model Network created and assigned.

in1BDAStudy
updatedStudy

"MaterialsTechnologyStudy" is output having had its Associative Model Network, "MaterialsTechnologyStudy_AMN" assigned.

out1BDAStudy
VerificationEvidence

Model Instances and Key Value Instances are output as "VerificationEvidence" that will be used in the review stage of the study to determine the outcome of the study.

out1..*No type defined
AMN

The Associative Model Network, "MaterialsTechnologyStudy_AMN" is output.

out1BDAAssociativeModelNetwork
Call Behaviour: AddStudyAssociativeModelNetwork (from ../Behaviours/ArchitectureCockpit/SetupOrchestrate_trade_off_studies::DefineStudy)

Local name:AddStudyAssociativeModelNetwork

MaterialsTechnologyStudy" is input to the activity to have its Associative Model Network created and assigned.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
study

"MaterialsTechnologyStudy" is input to the activity to have its Associative Model Network created and assigned.

Input1BDAStudyMaterialsTechnologyStudy
updatedStudy

"MaterialsTechnologyStudy" is output having had its Associative Model Network, "MaterialsTechnologyStudy_AMN" assigned.

Output1BDAStudyMaterialsTechnologyStudy
newModelInstances

The new Model Instances, to be used as "VerificationEvidence" in the review stage of the study are created and output.

Output0..*BDAModelInstanceMB_CrankGearStructuralModel_2;
MB_CrankGearAnalysisResults_2;
MB_CrankGear_WConfidence_2
newModelInstancesInputsLinks

The "derivedFrom" references for for the Model Instances are output.

Output0..*BDAModelInstanceIsDerivedFromMB_Geom_model:derivedFrom;
MB_CrankGearStructuralModel_2:derivedFrom;
CompositeMaterial:derivedFrom
newKeyValueInstances

The new Key Value Instance, to be used as "VerificationEvidence" in the review stage of the study is created and output.

Output0..*BDAKeyValueInstanceMB_CrankGearWeight_2
newAssociativeModelNetwork

The Associative Model Network, "MaterialsTechnologyStudy_AMN" is output.

Output0..*BDAAssociativeModelNetworkMaterialsTechnologyStudy_AMN
newPlan

No output required.

Output0..1No type definedNo connection found

Package: AddModelsToAssociativeModelNetwork

Activity: AddModelsToAssociativeModelNetwork

(from Package:AddModelsToAssociativeModelNetwork)

How objects are related is defined within this activity.

Figure:act_WPEx_AddModelsToAssociativeModelNetwork

Block Block Block Block

Figure:bdd_WPEx_MaterialsTechnologyStudy_AMN_ToArch

Table: AddModelsToAssociativeModelNetwork Parameters

Name Notes Direction Multiplicity Type
Architecture

The Architecture, "MB_Architecture_2" is input as the architecture for "MaterialsTechnologyStudy".

in1BDAArchitecture
breakdownElement

The breakdown element of interest to the study for improvement is output as "MB_CrankGears".

out1BDABreakdownElement
AnalysisResults

The Analysis Results of this study are stored in "MB_CrankGearAnalysisResults_2", here the container for these results is output ready to be populated.

out1BDAModelInstance
Call Behaviour: Select (from ../Behaviours/ArchitectureCockpit::LocalGenericBehaviours)

Local name:Select

The focus point of the study "MB_CrankGears" is selected.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
selectedItem

The breakdown element, "MB_CrankGears" is selected.

Output1..*No type definedMB_CrankGears
Call Behaviour: Select (from ../Behaviours/ArchitectureCockpit::LocalGenericBehaviours)

Local name:Select

"MB_CrankGearAnalysisResults_2" is selected as a realization of the need to improve the breakdown element "MB_CrankGears".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
selectedItem

The realization item, "MB_CrankGearAnalysisResults_2" is selected.

Output1..*No type definedMB_CrankGearAnalysisResults_2
Call Behaviour: AddBreakdownElementRealizations (from ../Behaviours/ArchitectureCockpit/DefineManageVirtualArchitecture::DefineRealizations)

Local name:AddBreakdownElementRealizations

The association between "MB_CrankGears" and "MB_CrankGearAnalysisResults_2" is realised.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
breakdownElement

The breakdown element "MB_CrankGears is input.

Input1BDABreakdownElementMB_CrankGears
realizationItem

The realization item "MB_CrankGearAnalysisResults_2" is input.

Input1..*BDABreakdownElementRealizationItemMB_CrankGearAnalysisResults_2
association

The realisation element is output.

Output1..*BDABreakdownElementRealizationAssociationrealise
approvals

No output required.

Output0..*BDAApprovalNo connection found
assumptions

No output required.

Output0..*BDAAssumptionNo connection found
justifications

No output required.

Output0..*BDAJustificationNo connection found
Call Behaviour: IncludeElementsInArchitecture (from ../Behaviours/ArchitectureCockpit/DefineManageVirtualArchitecture::DefineArchitectures)

Local name:IncludeElementsInArchitecture

The realization relationship defined above is included in the architecture passed to the activity.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
architecture

The architecture is passed into the activity.

Input1BDAArchitectureBDAArchitecture
elementsToInclude

The realization relationship is input to be included.

Input1..*BDAArchitectureElementItemrealise
inclusion

The inclusion relationship between the architecture and realization relationship is output.

Output1..*BDAArchitectureElementInclusioninc
justifications

No output required.

Output0..*BDAJustificationNo connection found
assumptions

No output required.

Output0..*BDAAssumptionNo connection found
approvals

No output required.

Output0..*BDAApprovalNo connection found

Package: DefineStudyVerificationObjectives

Activity: DefineStudyVerificationObjectives

(from Package:DefineStudyVerificationObjectives)

The Verification Objectives which will be checked against later are assigned to the study here.

Figure:act_WPEx_DefineStudyVerificationObjectives

Block Block Block Block Block Block

Figure:bdd_WPEx_MaterialsTechnologyStudy_Models_ToReqts

Table: DefineStudyVerificationObjectives Parameters

Name Notes Direction Multiplicity Type
Study

The study, "MaterialsTechnologyStudy" is input here to have its verification objectives defined and assigned.

in1BDAStudy
updatedStudy

The "MaterialsTechnologyStudy" is output from the activity having now been assigned its verification objectives.

out1BDAStudy
breakdownElement

The breakdown element of the product, "MB_CrankGears" are input here to be used as a point of reference to be improved in the objectives.

in1No type defined
VerificationEvidence

Model Instances and Key Value Instances are input as "VerificationEvidence" that will be used in the review stage of the study to determine the outcome of the study.

in1..*No type defined
Requirements

The requirements of the study are input to the activity to be assigned to the study.

in1..*No type defined
Architecture

The architecture of the study is input to have the "satisfiedBy" conditions of the input requirements assigned.

in1BDAArchitecture
Call Behaviour: AddStudyVerificationObjectives (from ../Behaviours/ArchitectureCockpit/SetupOrchestrate_trade_off_studies::DefineStudy)

Local name:AddStudyVerificationObjectives

The Verification objectives are added to the study, "MaterialsTechnologyStudy".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
study

"MaterialsTechnologyStudy" is input into the activity for its Verification Objectives to be added.

Input1BDAStudyMaterialsTechnologyStudy
requirement

The requirement to be added to the study, "Weight10ReductionReqt" is input here.

Input0..*BDARequirementObjectWeight10ReductionReqt
objectsToSatisfy

The breakdown element "MB_CrankGears" is passed in as the object that is to be improved as part of the study.

Input0..*BDASatisfiedByObjectMB_CrankGears
objectsAsEvidence

"MB_CrankGearAnalysisResults_2" and "MB_CrankGearWeight_2" are input to be used as evidence that the Crank Gear Weight Requirement has been satisfied.

Input0..*BDAVerificationEvidenceObjectMB_CrankGearAnalysisResults_2;
MB_CrankGearWeight_2
updatedStudy

The updated version of "MaterialsTechnologyStudy" is output with the new Verification Objective added.

Output1BDAStudyMaterialsTechnologyStudy
verification

This is the link between the evidence that will show whether the requirement has been satisfied.

Output0..*BDAVerificationMB_CrankGearAnalysisResults_2:verification;
MB_CrankGearWeight_2:verification
satisfiedBy

The solution to the requirement is output as "CrankGearWeightReqtSatis".

Output0..*BDARequirementShouldBeSatisfiedCrankGearWeightReqtSatis
newRequirement

No output required.

Output0..*BDARequirementNo connection found
otherObjectsCreatedOrUpdated

No output required.

Output0..*BDAIdentifiableObjectNo connection found
Call Behaviour: AddStudyVerificationObjectives (from ../Behaviours/ArchitectureCockpit/SetupOrchestrate_trade_off_studies::DefineStudy)

Local name:AddStudyVerificationObjectives

The Verification objectives are added to the study, "MaterialsTechnologyStudy".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
study

"MaterialsTechnologyStudy" is input into the activity for its Verification Objectives to be added.

Input1BDAStudyMaterialsTechnologyStudy
requirement

The requirement to be added to the study, "WeightConfidenceReqt" is input here.

Input0..*BDARequirementObjectWeightConfidenceReqt
objectsToSatisfy

The breakdown element "MB_CrankGears" is passed in as the object that is to be improved as part of the study.

Input0..*BDASatisfiedByObjectMB_CrankGears
objectsAsEvidence

"MB_CrankGear_WConfidence_2" is input for use as evidence to prove that the Crank Gear Confidence Requirement has been satisfied.

Input0..*BDAVerificationEvidenceObjectMB_CrankGear_WConfidence_2
updatedStudy

The updated version of "MaterialsTechnologyStudy" is output with the new Verification Objective added.

Output1BDAStudyMaterialsTechnologyStudy
verification

This is the link between the evidence that will show whether the requirement has been satisfied.

Output0..*BDAVerificationMB_CrankGear_WConfidence_2:verification
satisfiedBy

The solution to the requirement is output as "CrankGearConfidenceReqtSatis".

Output0..*BDARequirementShouldBeSatisfiedCrankGearConfidenceReqtSatis
newRequirement

No output required.

Output0..*BDARequirementNo connection found
otherObjectsCreatedOrUpdated

No output required.

Output0..*BDAIdentifiableObjectNo connection found
Call Behaviour: AddStudyVerificationObjectives (from ../Behaviours/ArchitectureCockpit/SetupOrchestrate_trade_off_studies::DefineStudy)

Local name:AddStudyVerificationObjectives

The Verification objectives are added to the study, "MaterialsTechnologyStudy".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
study

"MaterialsTechnologyStudy" is input into the activity for its Verification Objectives to be added.

Input1BDAStudyMaterialsTechnologyStudy
requirement

The requirement to be added to the study, "GeomConstraint" is input here.

Input0..*BDARequirementObjectGeomConstraint
objectsToSatisfy

The breakdown element "MB_CrankGears" is passed in as the object that is to be improved as part of the study.

Input0..*BDASatisfiedByObjectMB_CrankGears
objectsAsEvidence

"MB_CrankGearStructuralModel_2" is input for use as evidence to prove that the Crank Gear Geometric Requirement has been satisfied.

Input0..*BDAVerificationEvidenceObjectMB_CrankGearStructuralModel_2
updatedStudy

The updated version of "MaterialsTechnologyStudy" is output with the new Verification Objective added.

Output1BDAStudyMaterialsTechnologyStudy
verification

This is the link between the evidence that will show whether the requirement has been satisfied.

Output0..*BDAVerificationMB_CrankGearStructuralModel_2:verification
satisfiedBy

The solution to the requirement is output as "CrankGearGeomReqtSatis".

Output0..*BDARequirementShouldBeSatisfiedCrankGearGeomReqtSatis
newRequirement

No output required.

Output0..*BDARequirementNo connection found
otherObjectsCreatedOrUpdated

No output required.

Output0..*BDAIdentifiableObjectNo connection found
Call Behaviour: IncludeElementsInArchitecture (from ../Behaviours/ArchitectureCockpit/DefineManageVirtualArchitecture::DefineArchitectures)

Local name:IncludeElementsInArchitecture

The architecture of the study is input to have the "satisfiedBy" condition, "CrankGearWeightReqtSatis" of the requirement, "Weight10ReductionReqt" assigned.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
architecture

The architecture of the study is input to have the "satisfiedBy" condition, "CrankGearWeightReqtSatis" of the requirement, "Weight10ReductionReqt" assigned.

Input1BDAArchitectureMB_Architecture_2
elementsToInclude

The "satisfiedBy" condition, "CrankGearWeightReqtSatis" of the requirement, "Weight10ReductionReqt" is input.

Input1..*BDAArchitectureElementItemCrankGearWeightReqtSatis
inclusion

The inclusion attached to "CrankGearWeightReqtSatis"

Output1..*BDAArchitectureElementInclusionCrankGearWeightReqtSatis:inc
justifications

No output required.

Output0..*BDAJustificationNo connection found
assumptions

No output required.

Output0..*BDAAssumptionNo connection found
approvals

No output required.

Output0..*BDAApprovalNo connection found
Call Behaviour: IncludeElementsInArchitecture (from ../Behaviours/ArchitectureCockpit/DefineManageVirtualArchitecture::DefineArchitectures)

Local name:IncludeElementsInArchitecture

The architecture of the study is input to have the "satisfiedBy" condition, "CrankGearConfidenceReqtSatis" of the requirement, "WeightConfidenceReqt" assigned.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
architecture

The architecture of the study is input to have the "satisfiedBy" condition, "CrankGearConfidenceReqtSatis" of the requirement, "WeightConfidenceReqt" assigned.

Input1BDAArchitectureMB_Architecture_2
elementsToInclude

The "satisfiedBy" condition, "CrankGearConfidenceReqtSatis" of the requirement, "WeightConfidenceReqt" is input.

Input1..*BDAArchitectureElementItemCrankGearConfidenceReqtSatis
inclusion

The inclusion attached to "CrankGearConfidenceReqtSatis"

Output1..*BDAArchitectureElementInclusionCrankGearConfidenceReqtSatis:inc
justifications

No output required.

Output0..*BDAJustificationNo connection found
assumptions

No output required.

Output0..*BDAAssumptionNo connection found
approvals

No output required.

Output0..*BDAApprovalNo connection found
Call Behaviour: IncludeElementsInArchitecture (from ../Behaviours/ArchitectureCockpit/DefineManageVirtualArchitecture::DefineArchitectures)

Local name:IncludeElementsInArchitecture

The architecture of the study is input to have the "satisfiedBy" condition, "CrankGearGeomReqtSatis" of the requirement, "GeomConstraint" assigned.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
architecture

The architecture of the study is input to have the "satisfiedBy" condition, "CrankGearGeomReqtSatis" of the requirement, "GeomConstraint" assigned.

Input1BDAArchitectureMB_Architecture_2
elementsToInclude

The "satisfiedBy" condition, "CrankGearGeomReqtSatis" of the requirement, "GeomConstraint" is input.

Input1..*BDAArchitectureElementItemCrankGearGeomReqtSatis
inclusion

The inclusion attached to "CrankGearGeomReqtSatis"

Output1..*BDAArchitectureElementInclusionCrankGearGeomReqtSatis:inc
justifications

No output required.

Output0..*BDAJustificationNo connection found
assumptions

No output required.

Output0..*BDAAssumptionNo connection found
approvals

No output required.

Output0..*BDAApprovalNo connection found

Package: PerformStudy

Activity: PerformStudy

(from Package:PerformStudy)

The study is launched and undertaken by the OEM teams and external suppliers.

Figure:act_WPEx_PerformStudy

Block Block Block Block Block Block

Table: PerformStudy Parameters

Name Notes Direction Multiplicity Type
Study

The "MaterialsTechnologyStudy" is taken from the activity Prepare Study to be executed in Perform Study.

in1BDAStudy
Assumption

Any reasonable assumptions made by the Supplier are output from the activity Perform Study to be reviewed in Review Study.

out1BDAAssumption
AMN

The new Associative Model Network associated with "MaterialsTechnologyStudy" is input to execute the study.

in1BDAAssociativeModelNetwork
Call Behaviour: ShareStudyInternally

Local name:ShareStudyInternally

The Study and Associative Model Network are passed into this activity to be shared internally with the OEM Simulation Experts using MoSSEC Web Services.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
Study

"MaterialsTechnologyStudy" is input to be shared internally.

Input1BDAStudyMaterialsTechnologyStudy
AMN

"MaterialsTechnologyStudy_AMN" is input to be shared internally.

Input1BDAAssociativeModelNetworkMaterialsTechnologyStudy_AMN
Call Behaviour: UpdateAMN

Local name:UpdateAMN

The Associative Model Network, "MaterialsTechnologyStudy_AMN" is input so that its "ModelInstances" and "derivedFrom" relationships can be defined.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
AMN

The Associative Model Network, "MaterialsTechnologyStudy_AMN" is input so that its "ModelInstances" and "derivedFrom" relationships can be defined.

Input1BDAAssociativeModelNetworkMaterialsTechnologyStudy_AMN
updatedAMN

The updated Associative Model Network is output.

Output1BDAAssociativeModelNetworkMaterialsTechnologyStudy_AMN
ModelInstance

The Model Instance, "MB_CrankGearMeshModel" is output so that it can be shared and update both Internally and Externally.

Output1BDAModelInstanceMB_CrankGearMeshModel
Call Behaviour: Select (from ../Behaviours/ArchitectureCockpit::LocalGenericBehaviours)

Local name:Select

"MB_CrankGearStructuralModel_2" is selected so that it can be updated as the results are returned from the OEM Simulation Experts.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
selectedItem

"MB_CrankGearStrucutralModel_2" is selected.

Output1..*No type definedMB_CrankGearStructuralModel_2
Call Behaviour: GenerateAndReturnResultsInternally

Local name:GenerateAndReturnResultsInternally

The OEM Simulation Experts return their expected results internally to the OEM Architect.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
ModelInstances

The two Model Instances, "MB_CrankGearMeshModel" and "MB_CrankGearStructuralModel_2" are input to be updated.

Input1..*BDAModelInstanceMB_CrankGearMeshModel;
MB_CrankGearStructuralModel_2
updatedModelInstances

The updated Model Instances, "MB_CrankGearMeshModel" and "MB_CrankGearStructuralModel_2" are output.

Output1..*BDAModelInstanceMB_CrankGearMeshModel;
MB_CrankGearStructuralModel_2
Call Behaviour: ExportSupplierData

Local name:ExportSupplierData

Appropriate data from the Crank Gear Mesh Model is extracted and sent to the Supplier Expert for analysis.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
Model

"MB_CrankGearMeshModel" is input here to be securely sent to the Supplier Expert.

Input1BDAModelInstanceMB_CrankGearMeshModel
Call Behaviour: ReturnSupplierOutcome

Local name:ReturnSupplierOutcome

The Supplier Expert returns to the Architect any assumptions made while asssessing the "MB_CrankGearMeshModel".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
Assumption

The Supplier Expert makes the assumption, "TemperatureAssumption" and this is output here.

Output1BDAAssumptionTemperatureAssumption

Package: ShareStudyInternally

Activity: ShareStudyInternally

(from Package:ShareStudyInternally)

The Study and Associative Model Network are passed into this activity to be shared internally with the OEM Simulation Experts using MoSSEC Web Services.

Figure:act_WPEx_ShareStudyInternally

Block Block Block Block Block Block Block Block Block Block Block Block Block Block

Figure:bdd_WPEx_PerformNotification

Figure:bdd_WPEx_MaterialsTechnologyStudy_AMN_ModelsAdapted

Table: ShareStudyInternally Parameters

Name Notes Direction Multiplicity Type
Study

"MaterialsTechnologyStudy" is input to be shared internally.

in1BDAStudy
AMN

"MaterialsTechnologyStudy_AMN" is input to be shared internally.

in1BDAAssociativeModelNetwork
Call Behaviour: Update (from ../Behaviours/ArchitectureCockpit::LocalGenericBehaviours)

Local name:Update

The status of the study is updated to "Launched".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
itemToUpdate

The Architects' local copy of MaterialsTechnologyStudy is passed in to have its status updated.

Input1..*No type definedMaterialsTechnologyStudy
updatedItem

The Architects' local copy of MaterialsTechnologyStudy is output after its status has been updated.

Output1..*No type definedMaterialsTechnologyStudy
Call Behaviour: sendNotifications (from ../Behaviours/ArchitectureCockpit/SetupOrchestrate_trade_off_studies::OrchestrateStudy)

Local name:sendNotifications

A Notification that the status of the "MaterialsTechnologyStudy" is sent from the OEM Architect to the OEM Simulation Experts, containing reference to "MaterialsTechnologyStudy" and "MaterialsTechnologyStudy_AMN".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
notfication

The Notification from the OEM Architect to the OEM Simulation Experts containg reference to "MaterialsTechnologyStudy" and "MaterialsTechnologyStudy_AMN".

Output1..*BDANotificationInWorkNotification
Call Behaviour: CallReadSOAPWebService (from ../Behaviours/ArchitectureCockpit::Recieve)

Local name:CallReadSOAPWebService

The OEM Simulation Experts use the information from "InWorkNotification" to Call Read SOAP Web Serivces to collect the Meta Data relating to "MaterialsTechnologyStudy" and stores this locally.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
objects

The OEM Architect receives the Read SOAP Request and passes the Meta-Data of their copy of "MaterialsTechnologyStudy" to the OEM Simulation Experts through SOAP Web Services.

Input1No type definedMaterialsTechnologyStudy
objects

The OEM Simulation Experts receive the Meta-Data of "MaterialsTechnologyStudy" from the OEM Architect through SOAP Web Services.

Output1No type definedMaterialsTechnologyStudy
Call Behaviour: CallReadSOAPWebService (from ../Behaviours/ArchitectureCockpit::Recieve)

Local name:CallReadSOAPWebService

The OEM Simulation Experts use the information from "InWorkNotification" to Call Read SOAP Web Serivces to collect the Meta Data relating to "MaterialsTechnologyStudy_AMN" and stores this locally.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
objects

The OEM Architect receives the Read SOAP Request and passes the Meta-Data of their copy of "MaterialsTechnologyStudy_AMN" to the OEM Simulation Experts through SOAP Web Services.

Input1No type definedMaterialsTechnologyStudy_AMN
objects

The OEM Simulation Experts receive the Meta-Data of "MaterialsTechnologyStudy_AMN" from the OEM Architect through SOAP Web Services.

Output1No type definedMaterialsTechnologyStudy_AMN
Action: EnterStudyLoop

Local name:EnterStudyLoop

The OEM Simulation Expert will select from the Study's Meta-Data and on demand pull the data they require.

This has no arguments

Action: EnterAMNLoop

Local name:EnterAMNLoop

The OEM Simulation Expert will select from the AMN's Meta-Data and on demand pull the data they require.

This has no arguments

Action: ExitAMNLoop

Local name:ExitAMNLoop

The OEM Simulation Experts exit the loop once they have pulled all of the data they require from "MaterialsTechnologyStudy_AMN".

This has no arguments

Action: ExitStudyLoop

Local name:ExitStudyLoop

The OEM Simulation Experts exit the loop once they have pulled all of the data they require from "MaterialsTechnologyStudy".

This has no arguments

LoopNode: StudyLoopNode

(from Activity:ShareStudyInternally)

The OEM Simulation Expert will select from the

 

Study's Meta-Data and on demand pull the

 

data they require.

This Activity has no parameters

Call Behaviour: DisplayMeta-Data (from ../Behaviours/ArchitectureCockpit::Visualization)

Local name:StudyLoop::DisplayMeta-Data

The system will display the Meta-Data of "MaterialsTechnologyStudy" for the OEM Simulation Experts.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
objectsToDisplay

"MaterialsTechnologyStudy" is input into the activity so that the system can display its Meta-Data for the OEM Simulation Experts.

Input1..*BDAIdentifiableObjectMaterialsTechnologyStudy
Call Behaviour: Select (from ../Behaviours/ArchitectureCockpit::LocalGenericBehaviours)

Local name:StudyLoop::Select

The OEM Simulation Experts select the data they wish to pull from the OEM Architect's copy of "MaterialTechnologyStudy" using the displayed Meta-Data.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
selectedItem

The reference to the data wished to be pulled from the OEM Architect's copy of "MaterialsTechnologyStudy" is output.

Output1..*No type definedType Not Defined
Call Behaviour: CallReadSOAPWebService (from ../Behaviours/ArchitectureCockpit::Recieve)

Local name:StudyLoop::CallReadSOAPWebService

The OEM Simulation Experts request using SOAP Web Services data contained within the OEM Architect's copy of "MaterialsTechnologyStudy".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
objects

The reference to the data contained within the OEM Architect's copy of "MaterialsTechnologyStudy" is input to be used as part of the Read SOAP Web Services Request packet to the OEM Architect.

Input1No type definedType Not Defined
objects

The requested data from the OEM Architect's copy of "MaterialsTechnologyStudy" is received and output.

Output1No type definedMaterialsTechnologyStudy
LoopNode: AMNLoopNode

(from Activity:ShareStudyInternally)

The OEM Simulation Expert will select from the

 

AMN's Meta-Data and on demand pull the

 

data they require.

This Activity has no parameters

Call Behaviour: DisplayMeta-Data (from ../Behaviours/ArchitectureCockpit::Visualization)

Local name:AMNLoop::DisplayMeta-Data

The system will display the Meta-Data of "MaterialsTechnologyStudy_AMN" for the OEM Simulation Experts.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
objectsToDisplay

"MaterialsTechnologyStudy_AMN" is input into the activity so that the system can display its Meta-Data for the OEM Simulation Experts.

Input1..*BDAIdentifiableObjectMaterialsTechnologyStudy_AMN
Call Behaviour: Select (from ../Behaviours/ArchitectureCockpit::LocalGenericBehaviours)

Local name:AMNLoop::Select

The OEM Simulation Experts select the data they wish to pull from the OEM Architect's copy of "MaterialTechnologyStudy_AMN" using the displayed Meta-Data.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
selectedItem

The reference to the data wished to be pulled from the OEM Architect's copy of "MaterialsTechnologyStudy_AMN" is output.

Output1..*No type definedType Not Defined
Call Behaviour: CallReadSOAPWebService (from ../Behaviours/ArchitectureCockpit::Recieve)

Local name:AMNLoop::CallReadSOAPWebService

The OEM Simulation Experts request using SOAP Web Services data contained within the OEM Architect's copy of "MaterialsTechnologyStudy_AMN".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
objects

The reference to the data contained within the OEM Architect's copy of "MaterialsTechnologyStudy_AMN" is input to be used as part of the Read SOAP Web Services Request packet to the OEM Architect.

Input1No type definedType Not Defined
objects

The requested data from the OEM Architect's copy of "MaterialsTechnologyStudy_AMN" is received and output.

Output1No type definedMaterialsTechnologyStudy_AMN

Package: UpdateAMN

Activity: UpdateAMN

(from Package:UpdateAMN)

The Associative Model Network, "MaterialsTechnologyStudy_AMN" is input so that its "ModelInstances" and "derivedFrom" relationships can be defined.

Figure:act_WPEx_UpdateAMN

Block

Figure:bdd_WPEx_MaterialsTechnologyStudy_AMN_ModelsAdapted

Table: UpdateAMN Parameters

Name Notes Direction Multiplicity Type
AMN

The Associative Model Network, "MaterialsTechnologyStudy_AMN" is input so that its "ModelInstances" and "derivedFrom" relationships can be defined.

in1BDAAssociativeModelNetwork
updatedAMN

The updated Associative Model Network is output.

out1BDAAssociativeModelNetwork
ModelInstance

The Model Instance, "MB_CrankGearMeshModel" is output so that it can be shared and update both Internally and Externally.

out1BDAModelInstance
Call Behaviour: UpdateAssociativeModelNetwork (from ../Behaviours/ArchitectureCockpit/SetupOrchestrate_trade_off_studies::UpdateStudy)

Local name:UpdateAssociativeModelNetwork

The Associative Model Network, "MaterialsTechnologyStudy_AMN" is input so that its "ModelInstances" and "derivedFrom" relationships can be defined.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
associativeModelNetwork

The Associative Model Network, "MaterialsTechnologyStudy_AMN" is input so that its "ModelInstances" and "derivedFrom" relationships can be defined.

Input1BDAAssociativeModelNetworkMaterialsTechnologyStudy_AMN
otherInputs

No input required.

Input0..*No type definedNo connection found
updatedAssociativeModelNetwork

The updated Associative Model Network, "MaterialsTechnologyStudy_AMN" is output.

Output0..*BDAAssociativeModelNetworkMaterialsTechnologyStudy_AMN
newOrUpdatedModelInstances

The "ModelInstances" associated to the Associative Model Network, "MaterialsTechnologyStudy_AMN" are output here.

Output0..*BDAModelInstanceMB_CrankGearSimplifiedGeomModel;
MB_CrankGearMeshModel;
MB_CrankGearWeightConfidenceModel
newOrUpdatedModelInstancesInputsLinks

The "derivedFrom" relationships are output here.

Output0..*BDAModelInstanceIsDerivedFromMB_CrankGearStructuralModel_2:derivedFrom;
MB_CrankGearSimplifiedGeomModel:derivedFrom;
MB_CrankGearAnalysisResults_2:derivedFrom;
MB_CrankGearMeshModel:derivedFrom
newOrUpdatedKeyValueInstances

No output required.

Output0..*BDAKeyValueInstanceNo connection found
updatedPlan

No output required.

Output0..1No type definedNo connection found

Package: GenerateAndReturnResultsInternally

Activity: GenerateAndReturnResultsInternally

(from Package:GenerateAndReturnResultsInternally)

The OEM Simulation Experts return their expected results internally to the OEM Architect.

Figure:act_WPEx_GenerateAndReturnResultsInternally

Block Block

Figure:bdd_WPEx_MaterialsTechnologyStudy_AMN_ModelResults

Table: GenerateAndReturnResultsInternally Parameters

Name Notes Direction Multiplicity Type
ModelInstances

The two Model Instances, "MB_CrankGearMeshModel" and "MB_CrankGearStructuralModel_2" are input to be updated.

in1..*BDAModelInstance
updatedModelInstances

The updated Model Instances, "MB_CrankGearMeshModel" and "MB_CrankGearStructuralModel_2" are output.

out1..*BDAModelInstance
Call Behaviour: GenerateModelInstanceResults (from ../Behaviours/ArchitectureCockpit/SetupOrchestrate_trade_off_studies::OrchestrateStudy)

Local name:GenerateModelInstanceResults

The Model Instance Results are generated for the new Structural Model.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
modelInstance

"MB_CrankGearStructuralModel_2" is input to have its results generated.

Input0..*BDAModelInstanceMB_CrankGearStructuralModel_2
updatedModelInstance

"MB_CrankGearStructuralModel_2" is updated with the new results documents and files.

Output0..*BDAModelInstanceMB_CrankGearStructuralModel_2
newDocuments

"MB_CrankGearStructuralResultsDoc" is output as the Model Instance Result Document.

Output0..*BDADocumentMB_CrankGearStructuralResultsDoc
newDigitalFiles

"MB_CrankGearStructuralResultsFile" is output as the Model Instance Result File.

Output0..*BDADigitalFileMB_CrankGearStructuralResultsFile
updatedKeyValues

No output required.

Output0..*BDAKeyValueInstanceNo connection found
newPropertyValues

No output required.

Output0..*BDAPropertyValueNo connection found
newQualityReport

No output required.

Output0..*BDAQualityReportInstanceNo connection found
Call Behaviour: GenerateModelInstanceResults (from ../Behaviours/ArchitectureCockpit/SetupOrchestrate_trade_off_studies::OrchestrateStudy)

Local name:GenerateModelInstanceResults

The Model Instance Results are generated for the Mesh Model.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
modelInstance

"MB_CrankGearMeshModel" is input to have its results generated.

Input0..*BDAModelInstanceMB_CrankGearMeshModel
updatedModelInstance

"MB_CrankGearMeshModel" is updated with the new results documents and files.

Output0..*BDAModelInstanceMB_CrankGearMeshModel
newDocuments

"MB_CrankGearMeshResultsDoc" is output as the Model Instance Result Document.

Output0..*BDADocumentMB_CrankGearMeshResultsDoc
newDigitalFiles

"MB_CrankGearMeshResultsFile" is output as the Model Instance Result File.

Output0..*BDADigitalFileMB_CrankGearMeshResultsFile
updatedKeyValues

No output required.

Output0..*BDAKeyValueInstanceNo connection found
newPropertyValues

No output required.

Output0..*BDAPropertyValueNo connection found
newQualityReport

No output required.

Output0..*BDAQualityReportInstanceNo connection found

Package: ExportSupplierData

Activity: ExportSupplierData

(from Package:ExportSupplierData)

Appropriate data from the Crank Gear Mesh Model is extracted and sent to the Supplier Expert for analysis.

Figure:act_WPEx_ExportSupplierData

Block Block Block Block Block Block

Figure:bdd_WPEx_SupplierPackageSend

Table: ExportSupplierData Parameters

Name Notes Direction Multiplicity Type
Model

"MB_CrankGearMeshModel" is input here to be securely sent to the Supplier Expert.

in1BDAModelInstance
Call Behaviour: Select (from ../Behaviours/ArchitectureCockpit::LocalGenericBehaviours)

Local name:Select

"MB_CrankGearAnalysisResults_2" is selected so that its status can be updated to "InWork".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
selectedItem

"MB_CrankGearAnalysisResults_2" is selected.

Output1..*No type definedMB_CrankGearAnalysisResults_2
Call Behaviour: Update (from ../Behaviours/ArchitectureCockpit::LocalGenericBehaviours)

Local name:Update

The status of "MB_CrankGearAnalysisResults_2" is updated to "InWork".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
itemToUpdate

"MB_CrankGearAnalysisResults_2" is input to be updated with the status "InWork".

Input1..*No type definedMB_CrankGearAnalysisResults_2
updatedItem

The updated "MB_CrankGearAnalysisResults_2" is output.

Output1..*No type definedMB_CrankGearAnalysisResults_2
Call Behaviour: sendNotifications (from ../Behaviours/ArchitectureCockpit/SetupOrchestrate_trade_off_studies::OrchestrateStudy)

Local name:sendNotifications

"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.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
notfication

The notification, "SupplierNotification" is sent to the supplier.

Output1..*BDANotificationSupplierNotification
Call Behaviour: Select (from ../Behaviours/ArchitectureCockpit::LocalGenericBehaviours)

Local name:Select

The Results File (MB_CrankGearMeshResultsFile), Sender (SimulationExpert), Sending Organization (OEM), Recipient (SupplierExpert), Recipient Organization (Supplier), derivedFrom relationships are all selected to be used to create a secure package to be sent to the Supplier.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
selectedItem

The Results File (MB_CrankGearMeshResultsFile), Sender (SimulationExpert), Sending Organization (OEM), Recipient (SupplierExpert), Reciepient Organization (Supplier) are all selected.

Output1..*No type definedMB_CrankGearMeshResultsFile;
SimulationExpert;
OEM;
Supplier;
MB_CrankGearMeshModel:derivedFrom;
CompositeMaterial:derivedFrom
Call Behaviour: AddUpdateSecurityData

Local name:AddUpdateSecurityData

The OEM draws up a contract, "MB_Contract", which contains details on Copy Restrictions and Copy Restriction Usage terms to which the Supplier must adhere to when handling the Model, "MB_CrankGearMeshModel" and Results File, "MB_CrankGearMeshResultsFile".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
Model

"MB_CrankGearMeshModel" is input to be used to formulate a security contract.

Input1BDAModelInstanceMB_CrankGearMeshModel
ResultsFile

"MB_CrankGearMeshResultsFile" is input to be used to formulate a security contract.

Input1BDADigitalFileMB_CrankGearMeshResultsFile
sendPerson

"MB_CrankGearMeshResultsFile" is input to be used to formulate a security contract.

Input1BDAPersonSimulationExpert
recipientPerson

"SupplierExpert" is input to be used to formulate a security contract.

Input1BDAPersonSupplierExpert
sendOrganization

"OEM" is input to be used to formulate a security contract.

Input1BDAOrganizationOEM
recipientOrganization

"Supplier" is input to be used to formulate a security contract.

Input1BDAOrganizationSupplier
Contract

"MB_Contract" is output as the contract.

Output1BDAContractMB_Contract
CopyRestrictionUsage

"CopyRestrictionUsage" is ouptut.

Output1BDAInformationUsageRightCopyRestrictionUsage
CopyRestriction

"CopyRestriction" is output.

Output1BDAInformationRightCopyRestriction
Call Behaviour: SendViaFileExchange (from ../Behaviours/ArchitectureCockpit::Send)

Local name:SendViaFileExchange

The package containing the Crank Gear Mesh Model, Results File and Security Contract are sent to the Supplier via File Exchange.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
objectsToSend

The package containing the Crank Gear Mesh Model, Results File and Security Contract is input.

Input1No type definedNo type defined
Package: AddUpdateSecurityData
Activity: AddUpdateSecurityData

(from Package:AddUpdateSecurityData)

The OEM draws up a contract, "MB_Contract", which contains details on Copy Restrictions and Copy Restriction Usage terms to which the Supplier must adhere to when handling the Model, "MB_CrankGearMeshModel" and Results File, "MB_CrankGearMeshResultsFile".

Table: AddUpdateSecurityData Parameters

Name Notes Direction Multiplicity Type
Model

"MB_CrankGearMeshModel" is input to be used to formulate a security contract.

in1BDAModelInstance
ResultsFile

"MB_CrankGearMeshResultsFile" is input to be used to formulate a security contract.

in1BDADigitalFile
sendPerson

"MB_CrankGearMeshResultsFile" is input to be used to formulate a security contract.

in1BDAPerson
sendOrganization

"OEM" is input to be used to formulate a security contract.

in1BDAOrganization
recipientPerson

"SupplierExpert" is input to be used to formulate a security contract.

in1BDAPerson
recipientOrganization

"Supplier" is input to be used to formulate a security contract.

in1BDAOrganization
Contract

"MB_Contract" is output as the contract.

out1BDAContract
CopyRestrictionUsage

"CopyRestrictionUsage" is ouptut.

out1BDAInformationUsageRight
CopyRestriction

"CopyRestriction" is output.

out1BDAInformationRight

Package: ReturnSupplierOutcome

Activity: ReturnSupplierOutcome

(from Package:ReturnSupplierOutcome)

The Supplier Expert returns to the Architect any assumptions made while asssessing the "MB_CrankGearMeshModel".

Figure:act_WPEx_ReturnSupplierOutcome

Block Block Block Block Block

Figure:bdd_WPEx_SupplierPackageReceived

Table: ReturnSupplierOutcome Parameters

Name Notes Direction Multiplicity Type
Assumption

The Supplier Expert makes the assumption, "TemperatureAssumption" and this is output here.

out1BDAAssumption
Call Behaviour: Select (from ../Behaviours/ArchitectureCockpit::LocalGenericBehaviours)

Local name:Select

The Supplier selects the Crank Gear Analysis Results which are to be updated.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
selectedItem

"MB_CrankGearAnalysisResults_2" is selected.

Output1..*No type definedMB_CrankGearAnalysisResults_2
Call Behaviour: GenerateModelInstanceResults (from ../Behaviours/ArchitectureCockpit/SetupOrchestrate_trade_off_studies::OrchestrateStudy)

Local name:GenerateModelInstanceResults

New Model Instance Results are generated.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
modelInstance

The Crank Gear Analysis Results are input by the Supplier Expert to generate new results documentation.

Input0..*BDAModelInstanceMB_CrankGearAnalysisResults_2
updatedModelInstance

"MB_CrankGearAnalysisResults_2" is updated by the Supplier Expert.

Output0..*BDAModelInstanceMB_CrankGearAnalysisResults_2
newDocuments

The document "RB_CrankGearAnalysisResultsDoc" is created.

Output0..*BDADocumentRB_CrankGearAnalysisResultsDoc
newDigitalFiles

The file "RB_CrankGearAnalysisResultsFile" is created.

Output0..*BDADigitalFileRB_CrankGearAnalysisResultsFile
updatedKeyValues

"MB_CrankGearWeight_2" is updated as the new ModelInstanceResults have been generated by the Supplier Expert.

Output0..*BDAKeyValueInstanceMB_CrankGearWeight_2
newPropertyValues

No output required.

Output0..*BDAPropertyValueNo connection found
newQualityReport

No output required.

Output0..*BDAQualityReportInstanceNo connection found
Call Behaviour: Select (from ../Behaviours/ArchitectureCockpit::LocalGenericBehaviours)

Local name:Select

The Supplier Expert documents a description of any assumptions made when generating the Model Instance Results.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
selectedItem

"AssumptionDescription" is created and output by the Supplier Expert.

Output1..*No type definedAssumptionDescription
Call Behaviour: AddAssumptionToObjectWithContext (from ../Behaviours/ArchitectureCockpit/EvaluateConceptsDecide::Decide)

Local name:AddAssumptionToObjectWithContext

The Crank Gear Analysis Results are attached to assumptions made by the Supplier Expert which will be reviewed and approved by the OEM later.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
text

The Assumption Description is input to be formalized into an actual Assumption.

Input1No type definedAssumptionDescription
itemSubjectOfAssumption

The Crank Gear Analysis Results are input to have any desciptions of assumptions formalized into assumptions.

Input0..*BDAAssumedItemMB_CrankGearAnalysisResults_2
assumptionContextItem

No input required.

Input0..*BDAAssumptionContextItemNo connection found
relatedAssumptions

No input required.

Input0..*BDAAssumptionNo connection found
assumption

The formal assumption made by the Supplier Expert is output as "TemperatureAssumption".

Output1..*BDAAssumptionTemperatureAssumption
assumptionApprovals

No output required.

Output0..*BDAApprovalNo connection found
Call Behaviour: sendNotifications (from ../Behaviours/ArchitectureCockpit/SetupOrchestrate_trade_off_studies::OrchestrateStudy)

Local name:sendNotifications

The Supplier Expert sends the OEM a notification that they have assessed the data from the OEM and that they have made an assumption to be approved.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
notfication

The notifcation, "OEMNotification" is sent to the OEM and is output from "sendNotifications".

Output1..*BDANotificationOEMNotification

Package: ReviewStudy

Activity: ReviewStudy

(from Package:ReviewStudy)

The OEM Architect reviews the progress of any available results.

Figure:act_WPEx_ReviewStudy

Block Block Block

Figure:bdd_WPEx_ReviewApprovals

Table: ReviewStudy Parameters

Name Notes Direction Multiplicity Type
Assumption

Any assumptions made by the Supplier in Perform Study are input into Review Study to be reviewed.

in1BDAAssumption
Architecture

The Baseline Architecture output from Prepare Study is input into Review Study to be used as as supporting justification for the Suppliers assumptions to be approved by the OEM Simulation Expert.

in1BDAArchitecture
Call Behaviour: UpdateObjectWithApprovals (from ../Behaviours/ArchitectureCockpit::Common)

Local name:UpdateObjectWithApprovals

The Temperature Assumption is reviewed by the OEM and approved, thus updating the Assumption status to approved and creating "ApproveAssumption".

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
object

The Temperature Assumption is input to the activity for the OEM to approve.

Input1BDAObjectWithApprovalsTemperatureAssumption
updatedObject

The Temperature Assumption is output from the activity once approved by the OEM.

Output1BDAObjectWithApprovalsTemperatureAssumption
approvals

The approval object associated to the OEM approving the Temperature Assumption is output.

Output1..*BDAApprovalApproveAssumption
Call Behaviour: Select (from ../Behaviours/ArchitectureCockpit::LocalGenericBehaviours)

Local name:Select

The OEM details a "JustificationDescription" to justify why the assumption is being approved.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
selectedItem

"JustificationDescription" is created and output by the OEM.

Output1..*No type definedNo type defined
Call Behaviour: AddJustificationToObjectWithSupport (from ../Behaviours/ArchitectureCockpit/EvaluateConceptsDecide::Decide)

Local name:AddJustificationToObjectWithSupport

Justification for approving "TemperatureAssumption" is given here with support.

Table: Arguments

Name Notes Direction Multiplicity Type Connected To
itemToBeJustified

"TemperatureAssumption" is passed in as the assumption that is to be justified.

Input0..*BDAJustifiedItemTemperatureAssumption
itemSupportingJustification

"MB_ArchitectureBaseline" is input as supporting evidence to justify that the asumption can be approved.

Input0..*BDAJustificationSupportItemMB_ArchitectureBaseline
text

The OEMs "JustificationDescription" is passed in as a description detailing the justification.

Input1No type definedNo type defined
relatedJustifications

No input required.

Input0..*BDAJustificationNo connection found
justificationApprovals

The Justifications Approval updates the Approval (ApproveAssumption) created previously for approving (TemperatureAssumption).

Output0..*BDAApprovalApproveAssumption
justification

"JustificationForApprovalOfAssumption" acts as the formal justification of the approval of "TemperatureAssumption".

Output1..*BDAJustificationJustificationForApprovalOfAssumption