One of the advantages of the SPDM systems is the centralization of data and the ability to record and trace all the modifications made to the simulation models, their inputs, and outputs. However, to maintain configuration control and their digital thread, these modifications must be controlled. While most SPDM Solutions available in the market take into consideration the business process associated to Change of inputs, these business processes are heavily dependent on the Organization. Even within an Organization, each Business Unit or Division might have different flows of data. In our experience, it is best practice to simplify and adapt the solution to the business needs, without involving complex processes or an abundance of information. This results in a faster adoption by users boosting the usage of the SPDM. The first step is to understand, and ideally harmonize, the flow of data and associated processes. Normally the simulation models are set on one side, with their inputs (such as Requirements, CAD models, Materials properties, Dependent simulation results), and on the other side their outputs or results, which could be linked to another items (namely Reports, Testing data, Documentation). From this perspective, any modification requested in the inputs must be analyzed prior to accepting them and generating new versions of the simulation model. In this paper, we will deep dive into the Impact Analysis portion of Change Control, and share some of the considerations that need to be taken. Bringing PLM’s Best Practices into the SPDM arena, We will answer the following questions: • How does a change in Input affect a Simulation Model ? • What are the consequences of a change in Input in a Simulation Model-Centric approach? • How to manage the data and keep traceability during the Impact Analysis process? • What is the added value of managing Impact Analysis inside SPDM? Finally, considering that Change Control of simulation models is crucial when Certifying by Analysis is in the works, we conclude that the importance of managing the whole Analysis Thread as and independent branch without affecting the Baseline during the impact analysis process. We will propose a data model that takes into consideration the scalability and the key nodes within the digital thread.