How can I sequence existing model or script tools within a larger model?

[JesseSchewe_mnr]

Hi,

When working in Model Builder, there are times where it'd be helpful for me to nest existing models or script tools in the one that I'm working on. An issue arises when I need these models/script tools within the model to run in a specific order. With normal geoprocessing tools this is straightforward; I can just plug the output data variable from one tool into the next and they must run in order. I'm also aware of using preconditions to prevent processes from running out of order, but tools need to take variables as preconditions and there aren't variables.

I've tried making a variable right in Model Builder that looks to where the output of the first tool should be to use as a precondition. It seems like that often evaluates before the specific data exists and causes the larger model to crash, and it can't check it multiple times throughout the run. I've also tried using the logical operator If Data Exists which can always lead to a run of the first tool, but not a way to run the second tool without a variable of the first to either put into the second or to merge the True/False branches off If Data Exists.

How can this be done with models/script tools? Is there a way to have them produce an output data variable that can be used in Model Builder? Is there a way to check if the tools are done? 

I'm open to clarifying questions and welcome any help! Thanks!

[DanPatterson · Accepted solution]

have you considered submodels?

Add a submodel to a model—ArcGIS Pro | Documentation

It might help isolate steps that need to be completed in a specific order/pattern

[JesseSchewe_mnr]

Hi Dan,

Thanks for providing that link. It explained model output parameters in a way that was much better for my understanding than the standard model parameters article. I learned to make models in a way that doesn't normally use parameters for the output data. Rather, the models normally dump data in a location relative to the input parameters. Therefore, there were never any variables popping out of my models when I would plug them into other models.