Phase II: Adding System Specific Content
Adding System Specific Content
This requires the team to brainstorm what specific components/assemblies are exchangeable. The team needs to explore what data is currently available, what softwares the data is computed/stored, and if those softwares can be connected to via digital thread.
While Phase I focused on creating the backbone, Phase II focuses on putting meat on the framework. This will require gathering and implementing domian specific knowldege from subject matter experts.
Phase II Steps
Note: When steps happen in parallel they are labelled on the same reference point in the diagram.
Step 4)
Threads Buildout: Add value property "hooks" where threads will connect and investigate threading details
Determining what parameters are passed from software to software and implementing the correct architecture to send and receive these value properties appropriately.
Step 5)
Report Generation: Create VTL Scripts
Revert back to the interaction map and determine what data needs to be passed from domain to domain. Work with the receiving domain to determine what format they would like to consume the data. Generate an automatic report to provide that domain with their required data.
Step 6)
Manually Added Content & 1st Order Equations
It is often difficult to implement a detailed thread and a first order "placeholder" is needed to do some high level math. These added equations can allow the model to be much more robust quickly. If there is no 1st order equation in place there is no way to estimate how domains interact. It may make since to start with mass, cost, maturity, & risk rollups and then add some system performance details such as endurance, payload weight, comms range, speed, etc. It is important to string together multiple different domains in order to gain a more robust well-rounded model.
Different Methods To Scale Model
There are many practical ways to scale the model and the team lead should always be absorbing new information and acting in an agile way to implement the new data. The team can: look for more data sources in which they can eventually thread, scale the number of model domains, complete threads to existing known data sources, or increase fidelity of model domains without threads.
Note: It is best to prioritize having the threads providing the depth rather than manually adding medium levels of fidelity to the model because as you add fidelity, your chance of rework increases.
PHASE II STARTING POINT
This diagram is a potential place your project will be when entering phase II. The 4 diagrams below show the different options available to scale the model. It is suggested that you "grab the low hanging fruit", pick the easiest alternative to scale if no path is being forced on you. If all paths seem relatively equal in difficulty, push away from alternative 4.
ALTERNATIVE 1
Scale Number of Model Domains
ALTERNATIVE 2
Investigate Other External Sources
ALTERNATIVE 3
Complete Realized Threads
ALTERNATIVE 4
Add Fidelity to Cameo